On 13/12/2013 21:01, David C. Rankin wrote:
On 12/13/2013 09:48 AM, David C. Rankin wrote:
If network-ups-tools doesn't exists anymore, then what is a good link that
describes how to correctly update the pkgbuild so it creates the needed
/usr/lib/systemd/system/ entries and sets/loads the correct usbhid driver?
Found:
https://wiki.archlinux.org/index.php/DeveloperWiki:Systemd
Are there any other favorites you guys have used when converting everything to
systemd?
Now here's a coincidence. I've just spent a fair part of the last 2 days
trying to get NUT working in a new Arch install (2013-12) - it isn't my
main system, just trying to understand Arch and systemd so I had a bit
of difficulty getting to grips with them. I did not find a great deal of
help (on this specific topic) out on the net although there were bits
and pieces to be had which finally came together.
The package is in the AUR as network-ups-tools and does supply the
systemd scripts - I used <yaourt -Sa network-ups-tools> IIRC. The
scripts to user are in /usr/lib/systemd/system and after configuring NUT
correctly, enabled for reboot with <systemctl enable nut-server.service>
and <systemctl start nut-server.service>. The same for nut-monitor.service.
Don't try to start nut-driver.service. It is started automatically by
the server when needed - so I understand.
My UPS is monitored through a serial interface and a problem that did
not resolve was the ownership of /dev/ttyS0. Udev (or something) insists
on creating the device owned by root and uucp and I could not get around
this. Eventually added user ups to the uucp group which solved it rather
unsatisfactorily.
HTH
Bill
