Boot hangs for 3 minutes at "Starting syslogd daemons"
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Boot hangs for 3 minutes at "Starting syslogd daemons"
Hi, everybody.
Whenevery I boot up my Slackware 10/10.1 boxes, the boot hangs for about 3 minutes at "starting syslogd daemons". After that it boots normally. This has been puzzling me because this happens on one box with 10, one with 10.1, and DOESN'T happen on another of my 10.1 boxes.
Take a look at the init scripts in /etc/rc.d/ find the file where syslogd is started and see what it does next, so you can find the bottleneck (usually hotplug checking for a hardware or dhcp looking for a lease).
After syslogd, in rc.M, is pcmcia, which I just disabled, to no effect. After that is is rc.inet1, which is set to a static IP. After that is hotplug, which, as you say, may well be the problem. What can I do to fix it?
Also, I thought this was kind-of weird. When booting, only the first command in the script is displayed, then the long wait, then the second, like this:
Starting sysklogd daemons: /usr/sbin/syslogd
[long wait, then changes to this:]
Starting sysklogd daemons: /usr/sbin/syslogd /usr/sbin/klogd -c 3 -x
The only thing between the two commands is "sleep 1". What do you make of this?
Very weird problem, it seems syslogd is doing something but I've never seen that behaviour. Maybe you should search the web, but before that, confirm the problem.
You can do that by stopping and re-running the service with: /etc/rc.d/rc.syslog stop && /etc/rc.d/rc.syslog start
If it takes 30 seconds, read the man page for some information or search the web.
You could also append a & at the end of the line that executes the daemon to start it on background (it will still take 30 seconds but will do it on background).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.