From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2)
Gecko/20040308

sysklogd-1.4.1-15

Description of problem:
[root@linux-laptop root]# syslogd -m 0
Terminated
[root@linux-laptop root]# echo $?
143

[root@linux-laptop root]# service syslog start
Starting system logger:                                    [FAILED]
Starting kernel logger:                                    [  OK  ]

On my machine most of the time issuing the commands above
results in preliminary death of syslogd. I've checked 
the source RPM and it seems to me that the line the following
snippet allow for a race resulting in the behaviour above:

                if (!check_pid(PidFile))
                {
                        if (fork()) {
                                /*
                                 * Parent process
                                 */
                                signal (SIGTERM, doexit);
                                sleep(300);

I think it is too late to arm the singal handler at 
that point - it should be done earlier.

This is not a showstopper bug, but it think its
worth fixing. At least "service" wont say that
syslogd failed when it actually succeeded.


Version-Release number of selected component (if applicable):
sysklogd-1.4.1-15

How reproducible:
Sometimes

Steps to Reproduce:
1. Try to start "syslogd -m 0" from the command line
   until it is terminated by a SIGTERM signal. Maybe
   one needs to try harder on some machines.

Actual Results:  syslogd parent is killed by SIGTERM.

Expected Results:  syslogd parent should catch the signal and exit
cleanly.

Additional info: