Citeren Niels Kristian Jensen <[email protected]>:

n...@grisen:~$ sudo su -
r...@grisen:~# cd /var/run/nut/
r...@grisen:/var/run/nut# ls -al
total 8
drwxrwx---  2 root nut  100 2010-11-12 14:31 .
drwxr-xr-x 16 root root 640 2010-11-19 09:58 ..
-rw-r--r--  1 nut  nut    5 2010-10-22 22:41 upsd.pid
-rw-r--r--  1 root root   5 2010-10-22 22:41 upsmon.pid
srw-rw----  1 nut  nut    0 2010-10-22 22:41 usbhid-ups-PingvinUPS

This is wrong. There is no usbhid-ups-PingvinUPS.pid file, although the UNIX domain socket is there. The only way how I can explain this is happening, if that you've started the usbhid-ups driver in a shell and somehow lost control over that shell while it kept running. Only when running in debug mode, no PID file is created since the process is running in the foreground so you can easily stop it (Ctrl-C).

Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)


_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Reply via email to