On 2.2.6-rmk1 syslogd does start. Both when /usr/sbin/syslogd is run at boot
and when I run it from a shell prompt it pauses for about 2 seconds then exits
(with zero), but it hasn't forked and left a background process. If I start it
with -d then it runs fine in the foreground, and I can ^Z bg it successfully.
If I try
/usr/sbin/syslogd -n
I get
Can't lock, lock is held by pid 32928.
This would appear to be my problem. (except that I don't get see this error
message when it auto-backgrounds. Might this be regarded as a bug?)
What can I do about this?
Does it relate to crond failing to run with:
/usr/sbin/crond: can't lock /var/run/crond.pid, otherpid may be 67107332: Invalid
argument
What do I do now?
Nick
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
