Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 8550 - Crashed INND will not be detected...
Crashed INND will not be detected...
Product: Red Hat Raw Hide
Classification: Retired
Component: initscripts (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
: 8791 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2000-01-17 16:02 EST by Enrico Scholz
Modified: 2014-03-16 22:12 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-24 12:18:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Enrico Scholz 2000-01-17 16:02:06 EST
The behavior of /etc/rc.d/rc.sysinit to delete all files in /var/run/*
(including /var/run/news/*)[1] leads to a possible loss of news articles.

/etc/rc.d/rc.news tries to detect a crashed innd by looking for
/var/run/news/innd.pid and recovers $ACTIVE then by using the "-r"
option[2]. But because rc.sysinit is deleting innd.pid _before_ $ACTIVE
will be renumbered, inconsistencies will be created.

# Clean up /var
# I'd use find, but /usr may not be mounted.
for afile in /var/lock/* /var/run/*; do
   if [ -d $afile ]; then
      rm -f $afile/*

##  Clean shutdown or already running?
if [ -f ${SERVERPID} ] ; then
    if kill -0 `cat ${SERVERPID}` 2>/dev/null; then
        echo 'INND is running'
        exit 0
    echo 'INND:  PID file exists -- unclean shutdown!'
Comment 1 Bill Nottingham 2000-01-24 12:18:59 EST
*** Bug 8791 has been marked as a duplicate of this bug. ***Will be fixed in initscripts-4.85 when it is released.

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