Description of problem: In Fedora 8 /sbin/newhidups has been replaced by /sbin/usbhid-ups, but the initscript for the 'ups' service hasn't been updated for that change. Version-Release number of selected component (if applicable): 2.2.0-3.fc8 How reproducible: 100% Steps to Reproduce: 1. /sbin/service ups start 2. 3. Actual results: An error message about not finding /sbin/newhidups . Expected results: Successful start of the ups monitor. Additional info: I made a sym link from /sbin/newhidups to /sbin/newhidups and things worked as expected.
I noticed some other initscript related issues which you might want to look at at the same time. The first is that the default /etc/sysconfig/ups file does not set MODEL which is used by the initscript, in particular for the killproc command. I set MODEL to upsdrvctl, but I was still seeing another problem. The stop (and restart) command was not killing off the newhidups process. kill -1 seemed to be ignored by that process, and if that's the default for the killproc function, that might be the problem.
You should not use $MODEL at all. It's been completely replaced by upsdrvctl. You're tight that the initscript must be fixed.
nut-2.2.0-6.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update nut'
I had already noticed the push to updates-testing. I will for sure test it by the end of the weekend, though I might get to it late tonight if I am still awake enough after computing gaming / watching football. I report back how it works after trying it out.
While I am sure I saw an email message about a nut 2.2 update, I am not seeing it in the updates-testing repository tonight. I'll take another look tomorrow.
There was discovered a regression in the init script. I had to unpush the update and issue another one (it's in pending state).
It doesn't look like it got pushed out last night, so it probably won't show up until Monday now. Is there some place I grab a copy from now? (I have a Fedora account (CLA only) if that helps.) This isn't critical for me, but I have time to try it this weekend if you want feedback early.
The koji build is here if you wish to test: http://koji.fedoraproject.org/koji/buildinfo?buildID=26031
nut-2.2.0-6.1.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update nut'
I installed 2.2.0-6.1 and tried it out. It looks like the newhidups error was my fault. That was referred to in a user part of /etc/ups/ups.conf. I am not sure of a good way to let people know of the change. Switching the driver name to usbhid-ups fixed the startup. There is still a problem with shutting the service down. The driver process is still left running. If I do service ups restart I end up with multiple usbhid-ups processes running.
This should not happen -- all the drivers should be terminated by the upsdrvctl program. Are you sure that those are not some of the previous instances? Could you please attach your ups.conf file, so I may try to reproduce the problem? Thank you for testing.
Created attachment 277021 [details] ups.conf I am sure the processes came from the ups service after the update. I have attached my ups.conf file.
nut-2.2.0-6.1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
Were you able to duplicate the issue of the driver not being killed when stopping the ups service?
No. I have also an usbhid-ups compatible ups and it works as expected. I'll try to investigate this again after I solve more urgent issues. I have released a package that works for me.