There appears to be an error in the FAQ: Q: When I tell upsd to reload the config files, it complains in the syslog that it can't open the upsd.conf. It read the files when it started up, so why is it failing now? A: Look at who upsd is running as now - use 'ps'. You'll probably see "nobody" in that first column, even though you started it as root. This is intentional - upsd drops root shortly after it starts up, but _after_ it gets done reading your config files. The last line is incorrect, looking at 'server/upsd.c' and from the behaviour of upsd. It used to be like that (if memory serves), but presently it drops root *before* reading the configuration files. So we either need to change the wording of the FAQ, or change the behaviour of 'upsd'. Any ideas/suggestions? Regards, Arjen
I would like to propose the attached patch, which will bring back the old (pre nut-1.3.0) behaviour (which is documented in the FAQ). Personally I like the idea of having the configuration files owned by 'root' and not being readable by the user running the daemons. If you happen to don't like that (and want to be able to send a SIGHUP to them and therefor give them at least read permission), this patch won't hurt you anyway. Any comments/suggestions before committing this? Regards, Arjen -------------- next part -------------- A non-text attachment was scrubbed... Name: upsd.diff Type: text/x-patch Size: 741 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20060208/f9a7fdcd/upsd.bin
Reasonably Related Threads
- Re: [nut-commits] svn commit r731
- [nut-Feature Requests][310492] Allow to specify hostnames in ACL (upsd.conf)
- Reserve '_' in driver names?
- trouble with ups mge evolution2200 and mandriva 2007 - nut 2. 2 + PSP
- Re: [nut-commits] svn commit r585 - in trunk: . conf server