On Sun, Oct 18, 2020 at 12:24:23PM +0200, Laurent Bigonville wrote:
> Le 17/10/20 à 19:05, David Engel a écrit :
> > On Sat, Oct 17, 2020 at 10:42:30AM +0200, Laurent Bigonville wrote:
> > > This is quite weird, the package already contains a systemd tmpfiles
> > > snippet
> > > (/usr/lib/tmpfiles
Le 17/10/20 à 19:05, David Engel a écrit :
On Sat, Oct 17, 2020 at 10:42:30AM +0200, Laurent Bigonville wrote:
This is quite weird, the package already contains a systemd tmpfiles snippet
(/usr/lib/tmpfiles.d/nut-client.conf) that should create the directory
during the boot.
I see the /usr/lib/
On Sat, Oct 17, 2020 at 10:42:30AM +0200, Laurent Bigonville wrote:
> This is quite weird, the package already contains a systemd tmpfiles snippet
> (/usr/lib/tmpfiles.d/nut-client.conf) that should create the directory
> during the boot.
I see the /usr/lib/tmpfiles.d/nut-client.conf now. It's be
On Sun, 24 May 2020 17:35:10 -0500 David Engel wrote:
> Dear Maintainer,
Hello David,
>
> I have two systems connected to a single UPS. The first system
> running both nut-server and nut-client packages works fine. The
> second system running only nut-client experiences this problem.
>
> Syste
Package: nut-client
Version: 2.7.4-12
Severity: important
Dear Maintainer,
I have two systems connected to a single UPS. The first system
running both nut-server and nut-client packages works fine. The
second system running only nut-client experiences this problem.
Systemd can't sucessfully st
5 matches
Mail list logo