On Sat, May 01, 1999 at 10:19:21AM +0100, Nicholas Clark wrote:
> 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
Cron checks that it isn't running 2 copies of itself by placing its pid in
/var/run/crond.pid. See:
$ cat /var/run/crond.pid
218
So it will refuse to run if that file exists. If you delete that file,
it should work. Do remember that you can strace programs which are
acting strangely - you can generally see where they are going wrong.
--
Matthew Wilcox <[EMAIL PROTECTED]>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
