[Nut-upsdev] bestfortress driver establishes/loses/establishes communication and so on...

[Michal Hlavinka]

Hi

> Hi Stuart
>
> 2012/1/19 Stuart D. Gathman<stuart at bmsi.com>:
>> Long ago, Nostradamus foresaw that on Jan 18, Arnaud Quette would write:
>>
>>> I really have to have a closer look there.
>>> I'm suspecting some race condition between upstart, sysV compat layer,
>>> udev and NUT starting, which could result in this.
>>
>>
>> Yes, on Fedora 16, you have to start nut-server before nut-monitor, and
>> systemd tries to start them at once.  Haven't got around to reporting that.
>> I don't think this problem is fortress specific.
>
> cc'ing Michal for this.
> I know that this was more a preliminary support than something really complete.

it *should* work :)

> quickly looking at the service files, nut-monitor is marked to be
> started after nut-server, and nut-server after nut-driver
> so you may be hitting a systemd bug.


could you please provide part from /var/log/messages, where 
nut-{driver,server} are being started? Also what systemd and nut version 
do you have (together with release number) ? rpm -q nut systemd

There is one bug in systemd, that breaks driver-server relation:
https://bugzilla.redhat.com/show_bug.cgi?id=704197, it was fixed 
recently, but it's still not available as update.

Michal