Nut upsuser - Oct 2013 - Is USBD necessary for average users?

I followed the NUT instructions that are on the projects site, I think,
and they said to set up USBD, so I did. Is that necessary for average
users using one PC (rather than servers), or will something not work
right if I reread and turn off USBD?

Hi David,

I also read the NUT user manual but I have seen no a? single mention of USBD.

You might mean upsd instead. If so then you might consider that an average
user might need access to information provided by UPS(es) such as the
status of UPS (on-line or on-battery, among others), of utility or of battery.
This information is cached and provided by upsd, and upsd is the server
clients communicate with, so it is absolutely necessary. Sorry if I answered
not the question you asked.

Regards,
Alexander.


???????,  1 ??????? 2013, 20:58 -07:00 ?? David N Melik <dchmelik at
hipplanet.com>:
>I followed the NUT instructions that are on the projects site, I think,
>and they said to set up USBD, so I did. Is that necessary for average
>users using one PC (rather than servers), or will something not work
>right if I reread and turn off USBD?
>
>
>
>_______________________________________________
>Nut-upsuser mailing list
>Nut-upsuser at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

-- 
????????? ????????
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20131004/15c344fa/attachment.html>

On Oct 1, 2013, at 11:58 PM, David N Melik wrote:
> I followed the NUT instructions that are on the projects site, I think,
^ The official NUT site? Feel free to post the URL.
> and they said to set up USBD, so I did. Is that necessary for average
> users using one PC (rather than servers), or will something not work
> right if I reread and turn off USBD?

I think Alexander explained upsd well, but here's some additional history
and explanation.

Question 10, Answer 2 of the FAQ
<http://www.networkupstools.org/docs/FAQ.html> points out that it is
possible to customize the NUT code, and combine upsmon and upsd into a single
daemon that talks to a driver. The disadvantage is that you wouldn't be able
to connect more than one client at a time, so debugging the driver with upsc
would no longer be possible.

Arnaud also experimented with writing a freedesktop.org HAL version of the
usbhid-ups driver. This was more suited to a single PC, and worked much like the
laptop battery power monitors, but HAL is deprecated now. We could certainly use
more help in this area - I think a lot of the people who have contributed to NUT
over the years have needed more of the "data center" functionality.

What are you trying to optimize?

-- 
Charles Lepple
clepple at gmail

On Fri, 4 Oct 2013 08:18:12 -0400
Charles Lepple <clepple at gmail.com> wrote:
> On Oct 1, 2013, at 11:58 PM, David N Melik wrote:
> 
> > I followed the NUT instructions that are on the projects site, I
> > think,
> 
> ^ The official NUT site? Feel free to post the URL.
> 
> > and they said to set up USBD, so I did. Is that necessary for
> > average users using one PC (rather than servers), or will something
> > not work right if I reread and turn off USBD?
> 
> 
> I think Alexander explained upsd well, but here's some additional
> history and explanation.
Thanks... and I did mean UPSD
> What are you trying to optimize?
nothing, but I just did not want another daemon running, or at least I
do not want a port open that can access the UPS, because I will not be
using it; it is more of a minor security issue than anything. The
instructions I read said to set up that port in NUT configuration, but I
would rather not set that.