[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#590882: marked as done (irqbalance: Broken handling of pidfile in init script)

Your message dated Tue, 23 Jul 2019 22:36:44 +0200
with message-id <fe635879-0f5f-96e0-ff8d-74aeca35d92b@ninthfloor.org>
and subject line Re: irqbalance: Broken handling of pidfile in init script
has caused the Debian Bug report #590882,
regarding irqbalance: Broken handling of pidfile in init script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
590882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590882
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: irqbalance
Version: 0.55-2.4lenny1
Severity: minor

Current stable verision of the package ships somewhat broken init script.
Specifically, starting the daemon currently implemented as:

start-stop-daemon --start --pidfile $PIDFILE \
		--name $PNAME --oknodo --startas $DAEMON \
	-- $OPTIONS $DOPTIONS

Which is good, except that /usr/sbin/irqbalance does not create a pidfile by
itself. So - pidfile does not actually got created.

And a result is that the 'stop' method of init script is unusable (it cannot
work without a pidfile).

Current unstable version of the package (0.56-1) handles a pidfile correctly.
Specifically, starting the daemon implemented there as:

pid=$( pidofproc -p $PIDFILE $DAEMON )
if [ -n "$pid" ] ; then
	log_begin_msg ". Already running"
	log_end_msg 0
	exit 0
fi  

start-stop-daemon --start --quiet --oknodo --exec $DAEMON -- $OPTIONS $DOPTIONS
pidofproc $PNAME > $PIDFILE

In fact, using an init script from unstable package 'solves' this issue.

Of course, using a package from an 'unstable' on a 'stable' may be out of 
question in many setups, hence this bug.

The desired resolution of this bug would be backporting the init script into
current stable version of the package.

-- System Information:
Debian Release: 5.0.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages irqbalance depends on:
ii  debconf [debconf-2.0]       1.5.24       Debian configuration management sy
ii  libc6                       2.7-18lenny4 GNU C Library: Shared libraries
ii  libglib2.0-0                2.16.6-3     The GLib library of C routines

irqbalance recommends no packages.

irqbalance suggests no packages.

-- debconf information:
  irqbalance/oneshot: false
  irqbalance/enable: true

--- End Message ---
--- Begin Message --- 
Version: 1.0.5-1

--- End Message ---
Reply to: