If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc).
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
Do you have any NIC/Wireless? I've read somewhere that when trying to boot, it goes through an iteration of configuring the network and at that point it tries several times to configure your network interfaces. It could be getting hung up there.
Thanks for your response..
Yes, I have a LAN and a wireless..
But this step, which takes too long, should be just starting of the logging daemon, right? The NIC is be configured by a different script..
Aren't all these messages "logged" only after the syslog is started?
What I mean is first the syslog is started (takes too long) and then the rest of the init scripts is executed which write to syslog.. So what I see here are the logs after the syslog is started
True and True, but why is it taking a long time? Does it only appear to, because after it starts, is something trying to write to it? That's the direction I'm heading and since you are able to get to it, then I know it did start. So now we track down what is causing its apparent slow start. First make sure it is there and running. It is. Now lets go further.
Ok, my problem was I did not have my hostname in the /etc/hosts so the syslog was trying to resolve it via nameserver and it was taking some time..
After adding it to /etc/hosts the syslog startup is ok
Comment