syslogd lockup or hang at startup

[Dave Littell]

Hi all,

I occasionally see syslogd hang at system startup.  The startup process
will issue a "failed (1:)" message after about 5 minutes and the system
will continue to boot, but syslogd is nowhere to be found.

Has anyone else seen this and (more importantly) know how to fix it?
One suggestion was to use "-m 0", but that didn't resolve this problem.


Thanks,
Dave