Public bug reported:
The packaging for nut-server assumes that host will also be a client, which is
an invalid assumption. As is stated <a
href="http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#DataRoom";>on
the nut website</a>:
<quote>Finally, there’s a special case. Type A systems are connected to a UPS’s
serial port, but don’t depend on it for power. This usually happens when a UPS
is physically close to a box and can reach the serial port, but the wiring is
such that it doesn’t actually feed it.</quote>
There is no good reason for nut=server to depend upon nut-client.
Furthermore, /etc/init.d/nut, in the start-stop-client() function should
not include "netserver" in the case $MODE... statement, or else a
different mode should be introduced which starts only the driver and
upsd components, as is described in the documentation.
It is a potentially dangerous and critical assumption that a nut host
will always be powered by, or only be powered by, a ups which it is also
monitoring. The software supports much greater freedom than this, and
the packaging should reflect this.
This is specifically in reference to the Precise (12.04.2 LTS) packaging
of nut-2.6.3-1ubuntu1.1, but the same dependency is observed to exist in
nut-2.7.1-1ubuntu1 for Trusty (14.04.1 LTS).
** Affects: nut (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418175
Title:
nut-server packaging incorrectly assumes host will be client, too
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1418175/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
