Bug 9643 - sysklogd-1.3.31 and "no such PID" error
Summary: sysklogd-1.3.31 and "no such PID" error
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysklogd
Version: 5.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-02-21 13:58 UTC by Alec Voropay
Modified: 2014-03-17 02:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-07-27 20:52:56 UTC
Embargoed:


Attachments (Terms of Use)

Description Alec Voropay 2000-02-21 13:58:40 UTC
After sysklogd upgrading I have error message on sysklogd stop :
====
[root@on ~]# /etc/rc.d/init.d/syslog stop
Shutting down kernel logger: klogd
kill: (1191) - No such pid

Shutting down system logger: syslogd
[root@on ~]#
====

The small research shows /etc/rc.d/init.d/functions :
====
# TERM first, then KILL if not dead
kill -TERM $pid
usleep 100000
if ps h $pid >/dev/null 2>&1 ; then
    sleep 3
    kill -KILL $pid
=====
The new "sysklogd-1.3.31-1.5" (from updates) dies VERY slow
on SIGTERM >100000 and second KILL can't find this PID.

Old "sysklogd-1.3-26" was OK.

Comment 1 Bill Nottingham 2000-08-08 02:36:42 UTC
In testing here, we cannot reproduce this. Sorry.


Note You need to log in before you can comment on or make changes to this bug.