Public bug reported:
Binary package hint: nut
It's barely possible that Ubuntu isn't vulnerable to this - I discovered
it, and did the actual smoke tests, on a Debian Lenny machine. The
problem is that the nut init script's powerdown function relies on
calling upsmon -K at a very late point, and that command fails, whcih
causes the script to imagine that the "kill ups" file is not present.
The reason for the failure is quite simple:
ma...@furrr:~$ ldd /sbin/upsmon
linux-vdso.so.1 => (0x00007ffff45fe000)
libupsclient.so.1 => /usr/lib/libupsclient.so.1 (0x00007f49ec001000)
libc.so.6 => /lib/libc.so.6 (0x00007f49ebc8f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f49ec207000)
I think we would all have to agree that there's no real use placing an
executable into /sbin when it depends on a library in /usr/lib, yes?
This issue exists present in Debian Lenny and Ubuntu Interpid. It
probably also affects Hardy and Gutsy, though they have a different sub-
minor version number; however, Debian Etch, with nut 2.0.4, already has
that in its init script. Etch is not affected by this bug because its
upsmon does NOT have the /usr/lib/libupsclient.so dependency. I haven't
any machines handy with Jaunty to check at this time.
** Affects: nut (Ubuntu)
Importance: Undecided
Status: New
--
NUT fails to shutdown UPS
https://bugs.launchpad.net/bugs/381269
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 list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
