Hi,
I'll fix/mitigate the race using the needed Wants/After against
udev-settle.service.
At the same time I don't think it's really coherent that:
When the driver is initially started and no device is present, the
driver immediately exits.
But when the driver is running and that the device is u
2012/8/11 Laurent Bigonville
> retitle 677143 nut-server: driver not always started when using systemd
> thanks
>
> Hello,
>
> Actually it seems that it's the driver which is not started properly:
>
> Aug 11 17:37:39 fornost upsd[1967]: Can't connect to UPS [ellipse]
> (usbhid-ups-ellipse): No s
retitle 677143 nut-server: driver not always started when using systemd
thanks
Hello,
Actually it seems that it's the driver which is not started properly:
Aug 11 17:37:39 fornost upsd[1967]: Can't connect to UPS [ellipse]
(usbhid-ups-ellipse): No such file or directory
Is it possible that /d
Hi (again),
Well the duplicate init script seems unrelated, I'll open an other bug
report for that.
Cheers
Laurent Bigonville
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
Well it seems that the old initscript have not been removed.
bigon@fornost:/etc/init.d$ ls -la nut*
-rwxr-xr-x. 1 root root 5345 sep 30 2011 nut
-rwxr-xr-x. 1 root root 5273 jun 2 16:45 nut-client
-rwxr-xr-x. 1 root root 5271 mai 2 22:29 nut-server
This is probably causing a race conditi
Package: nut-server
Version: 2.6.3-2
Severity: important
Hi,
Since the initscripts have been updated, it seems that from time to time
the server is not properly started and upsmon.
It then complains in the logs about:
Jun 11 22:01:32 fornost upsmon[1773]: Poll UPS [ellipse@localhost] failed -
D
6 matches
Mail list logo
