[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Package conflict apcupsd and nut-client

On Thu, 3 Oct 2019, Sebastian Hofmann wrote:

... Therefore I want to use both packages at the same time, but trying to install both results in a conflict between 'apcupsd' and 'nut-client'. Both provide and conflict 'ups-monitor':

This looks like a packaging problem, and an excessive use of the term 'ups-monitor'. It might be better to report it in the nut mailing list [1] and in the apcupsd mailing list [2].

If you run the apcupsd and the NUT upsd daemons at the same time, you will have to unify the back-end to get a reliable system shutdown. The apcupsd shell script apccontrol polls the daemon directly, but with NUT, an additional daemon upsmon polls the upsd daemon. To unify NUT's upsmon with apccontrol, you will have to use upsmon to feed NUT's upssched and then use upssched to feed the shell script which in NUT is often known as upssched-cmd. Maybe you could substitute an enhanced apccontrol for upssched-cmd and thus pick up all the events.

  UPS1 -> apcupsd -> apccontrol

  UPS2 -> upsd -> upsmon -> upssched -> apccontrol


[1] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
[2] https://sourceforge.net/projects/apcupsd/lists/apcupsd-users

Reply to: