Arjen de Korte wrote: > > > >> > Bus 003 Device 002: ID 050d:1100 Belkin Components > >> > > >> > # /lib/nut/usbhid-ups -a belkin > >> > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 > >> (2.2.0-) > >> > > >> > No matching HID UPS found > >> > > >> > Hmm best to stick with 2.0.4. > >> > >> No. Just run the driver in debug mode and you'll see what you have to do > >> to start it again. > > Perhaps we should lower the debug level of that particular set of > > error messages to 0? > > No, here the message should be send via fatalx or fatal_with_errno. The > upsdebugx and upsdebug_with_errno should remain reserved for debugging, > with levels > 0. I agree that drivers should be as verbose as possible if > it finds it can't connect.
Yes, but it's not a fatal error, because the user could have more than one UPS. You wouldn't want the driver to quit simply because the first UPS it found was unsupported. > > It seems to be useful even when not debugging. > > Other useful information should be logged via upslogx and > upslog_with_errno, which will also go to the console when we're not > backgrounded yet. Ah, yes! So this is what we should use for the above message, I think. -- Peter _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
