Bug 217320 - avahi init file does not clean properly after itself
avahi init file does not clean properly after itself
Product: Fedora
Classification: Fedora
Component: avahi (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Martin Bacovsky
Depends On:
  Show dependency treegraph
Reported: 2006-11-26 19:46 EST by Michal Jaegermann
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-01 18:17:39 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 Michal Jaegermann 2006-11-26 19:46:18 EST
Description of problem:

In /etc/rc.d/init.d

# ./avahi-daemon start
Starting Avahi daemon:                                     [  OK  ]
# ./avahi-daemon status
Avahi daemon is running
# pgrep -f -l avahi-d
8900 avahi-daemon: running [dyna0.local]
8901 avahi-daemon: chroot helper process

So far so good.  But now

# ./avahi-daemon stop
Shutting down Avahi daemon:                                [  OK  ]
# cat /var/run/avahi-daemon/pid
# ./avahi-daemon start
Starting Avahi daemon: Process 8900 died: No such process; removing PID file.
                                                           [  OK  ]

and similar stuff for './avahi-daemon restart', of course.

The issue is simple. /etc/rc.d/init.d/avahi-daemon script instead of
using 'killproc()' function is doing just '$AVAHI_BIN -k' and that leaves
behind a pid file for an already stopped process.

Another possibility - as '$AVAHI_BIN -D' clearly creates on its own 
/var/run/avahi-daemon/pid file then '$AVAHI_BIN -k' should take care
about cleaning it up on a succesful completion.

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

How reproducible:
Comment 1 Michal Jaegermann 2006-12-01 18:17:39 EST
Does not happen with avahi-0.6.15-3.fc7.

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