Bug 9643
| Summary: | sysklogd-1.3.31 and "no such PID" error | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Alec Voropay <alec> |
| Component: | sysklogd | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.2 | CC: | rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-07-27 20:52:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
In testing here, we cannot reproduce this. Sorry. |
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.