eth0 configured: eternal wait

I have just configued my eth0 device. It worked fine in the session in which
I did this. (amaong other things, tnx to the info from rihad and Ian in
another thread here).

Now I'm trying to restart my secondary Linux box and it goes into a
seemingly eternal wait after printing:

Starting system logger:

What can be the problem? Any suggestions?
___________________________________
Never mind the Bear, beware of papa...

PapaBear <(E-Mail Removed)> schreef in berichtnieuws
bgj631$lrd$1@news...
> I have just configued my eth0 device. It worked fine in the session in
which
> I did this. (amaong other things, tnx to the info from rihad and Ian in
> another thread here).
>
> Now I'm trying to restart my secondary Linux box and it goes into a
> seemingly eternal wait after printing:
>
> Starting system logger:
>
> What can be the problem? Any suggestions?

OK, updating as we speak: the system choose to continue after stating
"[FAILED]" after the system logger line

The same sort of situation occurs with:

Mounting other filesystems:

___________________________________
Never mind the Bear, beware of papa...

PapaBear wrote:
>
> PapaBear <(E-Mail Removed)> schreef in berichtnieuws
> bgj631$lrd$1@news...
> > I have just configued my eth0 device. It worked fine in the session in
> which
> > I did this. (amaong other things, tnx to the info from rihad and Ian in
> > another thread here).
> >
> > Now I'm trying to restart my secondary Linux box and it goes into a
> > seemingly eternal wait after printing:
> >
> > Starting system logger:
> >
> > What can be the problem? Any suggestions?
>
> OK, updating as we speak: the system choose to continue after stating
> "[FAILED]" after the system logger line
>
> The same sort of situation occurs with:
>
> Mounting other filesystems:

I assume this problem started after you got the network configured and
is therefore probably related to that.

Only guessing here. Longish pauses at boot time are often caused by DNS
issues. Depending on your configuration a DNS problem could cause
syslogd a problem, but I don't think it can effect mounting local
filesystems. If you have any NFS filesystems it can certainly affect
these.

To rule this out:

Ensure that the system can resolve itself. Put its IP address in
/etc/hosts and associate its hostname. Put the other one's address and
name in for good measure. Ensure that "files" appears on the "hosts:"
line in /etc/nsswitch.conf.

Do you have a nameserver? If so configure /etc/resolv.conf to point at
it. If not, put your ISP's nameservers in there. Ensure that "dns" also
appears on the hosts: line.

If this doesn't achieve anything then please describe your setup in a
bit more detail.

Regards, Ian