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

[Stuart D. Gathman]

Long ago, Nostradamus foresaw that on Jan 23, Michal Hlavinka would write:

>> After boot, only upsmon is running (and whining about no server)
>
> what output gives you following command?
>
> ll /etc/systemd/system/*target.wants/nut*.service

# ll /etc/systemd/system/*target.wants/nut*.service
lrwxrwxrwx. 1 root root 39 Dec  2 16:47 /etc/systemd/system/multi-user.target.wants/nut-monitor.service -> /lib/systemd/system/nut-monitor.service
lrwxrwxrwx. 1 root root 38 Dec  2 16:51 /etc/systemd/system/multi-user.target.wants/nut-server.service -> /lib/systemd/system/nut-server.service

>> and
>> messages contains:
>>
>> Jan 21 12:53:30 melissa systemd[1]: Service nut-driver.service is not
>> needed anymore. Stopping.
>
> this looks exactly as a symptom of the bug I mentioned in last email

I agree, and will report back when the promised systemd update makes it 
to the repo.

--
 	      Stuart D. Gathman <stuart at bmsi.com>
     Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.