Bug 77779 - nut--0.45.4 is very different from 0.45.0
nut--0.45.4 is very different from 0.45.0
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: nut (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Brian Brock
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-13 10:00 EST by Alain Spineux
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-20 11:23:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alain Spineux 2002-11-13 10:00:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
the use of nut-0.45.4 as changed
The main change is upsmon running as nobody, and cannot read files in /etc/ups 
and create /var/run/upssched.pipe


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install nut as a master
2. Setup a timer
3. start the ups service
3. unplug the power cord of the ups.


Actual Results:  
1. upsmon is started as nobody
2. upsmon don't start properly because it cannot read /etc/ups/upssched.conf 
(use upsmon -d in init.d to enable debuging in syslog)
3. upssched-cmd is not started because upsmon cannot 
create /var/run/upssched.pipe



Additional info:

The solution is to use the -p swith with upsmon in /etc/init.d to not start 
using an unprivileged uid. ( man upsmon )
And for the setup of a timer dont forget to uncomment PIPEFN in 
/etc/ups/upssched.conf

0.45.4 use a noew configuration file 

An better solution could be to use to nut 1.2 !
Comment 1 Ngo Than 2005-07-20 11:23:12 EDT
the problem should be fixed in current FC3/4 release. If it still appears,
please reopen it again. Please change the product to "Fedora Core" and
version to "4" in this case. Thank you very much

Note You need to log in before you can comment on or make changes to this bug.