** Also affects: nut (Ubuntu Jaunty)
Importance: Undecided
Status: New
--
nut init script reports incorrect status
https://bugs.launchpad.net/bugs/416182
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
** Changed in: nut (Ubuntu Jaunty)
Assignee: (unassigned) = Chuck Short (zulcss)
--
nut init script reports incorrect status
https://bugs.launchpad.net/bugs/416182
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
** Branch linked: lp:~zulcss/ubuntu/jaunty/nut/sru-416812
--
nut init script reports incorrect status
https://bugs.launchpad.net/bugs/416182
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
Ubuntu-server-bugs mailing
Statement of Impact:
Jaunty was shipped with a bug that if the user tries to query the status
of the nut daemons it, it returns the wrong information.
How to reproduce:
1. Install nut
2. Run the /etc/init.d/nut status script
3. Check to see if its running by comparing the output of ps auxwww |
$ sudo /etc/init.d/nut status
Checking status of Network UPS Tools
* upsd is not running
* upsmon is not running
[3]
$ ps auxww|grep ups
nut 6701 0.0 0.0 14668 784 ?Ss 08:13 0:00
/lib/nut/usbhid-ups -a myups2
nut 6703 0.0 0.0 14472 640 ?Ss 08:13
I should have mentioned I am using 2.4.1-3ubuntu1 on Ubuntu 9.10.
--
nut init script reports incorrect status
https://bugs.launchpad.net/bugs/416182
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
--
Ubuntu-server-bugs
This bug was fixed in the package nut - 2.4.1-3ubuntu2
---
nut (2.4.1-3ubuntu2) karmic; urgency=low
* debian/nut.init: Fix status_of_proc messages not to lie to
the user. (LP: #416182)
-- Chuck Short zul...@ubuntu.com Wed, 23 Sep 2009 09:37:16 -0400
** Changed in: nut
