On Wed, 04 Mar 2015 18:40:12 +0100 Michael Biebl
wrote:
> There are two ways how this could be addressed, I think:
>
> 1/ disabled systemd services shouldn't be started by invoke-rc.d
> This is a bug in sysv-rc and should be fixed irregardless of nut [1]
>
>
> 2/ nut could work-around this (for
There are two ways how this could be addressed, I think:
1/ disabled systemd services shouldn't be started by invoke-rc.d
This is a bug in sysv-rc and should be fixed irregardless of nut [1]
2/ nut could work-around this (for jessie), by using a dh_installinit
--error-handler function, which sim
On Sun, 1 Mar 2015, Sebastian Harl wrote:
I think that MODE=none should no longer be a valid option when using
systemd as you'd then use 'systemctl disable' instead. I don't know
systemd very well, so there could be other options as well and/or maybe
a way to disable upsmon in systemd by default
Hi,
On Mon, Feb 23, 2015 at 10:58:12AM -0500, Matthew Gabeler-Lee wrote:
> Unfortunately this bug is still present. A virgin install of nut-client
> results in a service start failure and thus package install failure.
>
> $ sudo systemctl status nut-monitor.service
> ● nut-monitor.service - Net
Package: nut-client
Version: 2.7.2-3
Followup-For: Bug #747863
Unfortunately this bug is still present. A virgin install of nut-client
results in a service start failure and thus package install failure.
$ sudo systemctl status nut-monitor.service
● nut-monitor.service - Network UPS Tools - pow
Le Tue, 10 Feb 2015 23:05:01 +0100,
Julien Cristau a écrit :
> On Tue, Feb 10, 2015 at 00:21:53 +0100, Laurent Bigonville wrote:
[...]
> >
> > What would be the opinion of the RT about this change?
> >
> We (or at least I) prefer to see proposed changes in the mail to
> having to look them up.
On Tue, Feb 10, 2015 at 00:21:53 +0100, Laurent Bigonville wrote:
> reopen 747863
> thanks
>
> Hello,
>
> As explained, I don't think the patch is complete and dropping
> the .service file so late in the release cycle doesn't seems a good
> idea.
>
> I've prepared a new upload that is actually
reopen 747863
thanks
Hello,
As explained, I don't think the patch is complete and dropping
the .service file so late in the release cycle doesn't seems a good
idea.
I've prepared a new upload that is actually restoring
the .service files and adding a wrapper around the executables.
Please see:
Package: nut
Version: 2.7.2-1
Followup-For: Bug #747863
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome
Package: nut-client
Version: 2.7.1-1
Hello,
nut-client's current systemd unit for upsmon is missing the init.d
script's check for the unconfigured "MODE=none" in /etc/nut/nut.conf.
This leads to a failed unit:
| Apr 27 10:41:43 laptop upsmon[2856]: Fatal error: insufficient power
configured!
|
10 matches
Mail list logo
