[Nut-upsuser] stopping ups services resets my network
aquette.dev at gmail.com
Wed Oct 28 09:23:35 UTC 2009
2009/10/27 Charles Lepple <clepple at gmail.com>:
> On Oct 27, 2009, at 11:56 AM, Arnaud Quette <aquette.dev at gmail.com> wrote:
>> 2009/10/27 Antoine Gatineau:
>> salut Antoine,
>>> I'm back again on this issue.
>>> I have contacted Red Hat support but they won't do anything to help since
>>> is not an official Red Hat package. Unless I prove the conflict come from
>>> So I am trying to figure out what is going on.
>>> Adding -DDDDD will not add any more log at the services stop.
>>> When I look at the sources, I couldn't find the piece of code that
>>> properly the usb UPS device. There is just a normal SIGTERM handling. Is
>>> this normal?
>> not at all, everything is clean here ;-)
>> what you're looking for is drivers/usbhid-ups.c->upsdrv_cleanup()
>> the comm_driver->close() will more specifically call, in your case,
>> the libusb.c backend, and so the usb_close() function.
>>> I also noticed that there are debug logs but I don't know how to activate
>>> them... Can somebody tell me how to do it?
>> I'm not sure for RHEL, but you should look around /etc/syslog.conf,
>> man syslog.conf and /var/log/debug
> Antoine may be referring to the debug information from the drivers but I
> don't think we have narrowed it down to something that can be resolved with
> those logs.
possible. imo, Antoine was talking about the few
"upslogx(LOG_DEBUG...", but it's quite possible that he was refering
to the upsdebugx().
Antoine: if you're refering to the latter, you should launch the
driver in debug mode, ie:
$ /path/to/usbhid-ups -DDDDD -a <upsname>
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
More information about the Nut-upsuser