Nut upsdev - Apr 2006 - Re: NUT docs bug & init-scripts for SuSE

>  Hello Arnaud,
Hi Alex,
>    First of all i want to thank you for such useful and convenient
> system tool as NUT. I think it is one from most important tools
> for server machines. And it make its work excellent.
thanks
>    I use NUT on SuSE distro and adapted init-scripts from package for
> this distro style. Send you them with hope that you find them useful
> for other users and may be include them in NUT package.
>    And one question. When i try use secure scheme that describe in
> 'docs/FAQ' (with 'nutdev' and 'nutsrv' users) i get
problem when
> i tested power race conditions. When i run command
>        /usr/local/ups/sbin/upsmon -c fsd
> at the end of 'halt' script i see:
> ---------------------------------------------------
> 
> Network UPS Tools - UPS driver controller 2.0.3
> Network UPS Tools (version 2.0.3) - APC Smart protocol driver
>          Driver version 1.99.7, command table version 2.0
> 
> Unable to open /dev/ttyS0: Permission denied
> 
>    Current user id: nutsrv (107)
> Serial port owner: nutdev (106)
> Serial port group: uucp (14)
>       Mode of port: 0600
> 
> Things to try:
> 
>   - Use another port (with the right permissions)
> 
>   - Fix the port owner/group or permissions on this port
> 
>   - Run this driver as another user (upsdrvctl -u or 'user=...' in 
> ups.conf).
>     See upsdrvctl(8) and ups.conf(5).
> 
> Fatal error: unusable configuration
> Driver failed to start (exit status=1)
> 
> -----------------------------------------------------
>    Same affect i can see when run command in shell:
>        /usr/local/ups/bin/upsdrvctl -u nutdev shutdown
>    I was forced return to 'nut:nut' scheme.
>    With best wishes,
first note that Stanislav Brabec (official NUT maintainer for SuSE)
is part of the NUT Team, and is taking care of the NUT packages.
He's currently updating these for SuSE 10.1...

For your above problem, you need to change the /dev/ttyS0
ownership to nutdev so that you can access the port in RW mode.
To do so, you need to look at udev. I've shipped udev scripts with
nut 2.0.3 as examples (these however need to be adapted.
Meanwhile, you can use some chown/chmod into the upsd init script...

Arnaud Quette
-- 
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060404/4e9d67ca/attachment.html

Arnaud QUETTE p??e v ?t 04. 04. 2006 v 09:05 +0200:
> 
> >  Hello Arnaud, 
> 
> Hi Alex, 
> 
> >    First of all i want to thank you for such useful and convenient
> > system tool as NUT. I think it is one from most important tools
> > for server machines. And it make its work excellent. 
> 
> thanks 
> 
> >    I use NUT on SuSE distro and adapted init-scripts from package
> for
> > this distro style. Send you them with hope that you find them useful
> > for other users and may be include them in NUT package.
In last month the nut SuSE scripts were completely rewrote, because old
scripts were not working as they come out of factory. You can try the
latest scripts from:
http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/
If you don't use SuSE Linux 10.1, you should download .src.rpm package
and recompile it for your version.

Improvements are welcome.
> >    And one question. When i try use secure scheme that describe in
> > 'docs/FAQ' (with 'nutdev' and 'nutsrv' users)
i get problem when
> > i tested power race conditions. When i run command
> >        /usr/local/ups/sbin/upsmon -c fsd
I am not sure, whether it is possible after quitting of upsd and
drivers.
> > -----------------------------------------------------
> >    Same affect i can see when run command in shell:
> >        /usr/local/ups/bin/upsdrvctl -u nutdev shutdown
> >    I was forced return to 'nut:nut' scheme.
> >    With best wishes,
Looking at the new package, it uses upsdrvctl shutdown with root
privileges, and it works (well, tested only with USB).
> first note that Stanislav Brabec (official NUT maintainer for SuSE) 
> is part of the NUT Team, and is taking care of the NUT packages. 
> He's currently updating these for SuSE 10.1... 
> 
> For your above problem, you need to change the /dev/ttyS0 
> ownership to nutdev so that you can access the port in RW mode.
If all commands with -u argument return this error, then it is a problem
of privileges. If only powerdown returns this error, then it is a
specific problem of late halt sequence.
> To do so, you need to look at udev. I've shipped udev scripts with 
> nut 2.0.3 as examples (these however need to be adapted. 
> Meanwhile, you can use some chown/chmod into the upsd init script... 
Well. This part is still missing in SuSE Linux 10.1. Most device things
were moved from udev to hal and we should decide, how exactly implement
it. Additionally, for serial UPS it will not help.

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SuSE CR, s. r. o.                             e-mail: sbrabec@suse.cz
Drahobejlova 27                               tel: +420 296 542 382
190 00 Praha 9                                fax: +420 296 542 374
Czech Republic                                http://www.suse.cz/