On Sun, Nov 17, 2024 at 07:01:51PM +0100, Andrea Bolognani wrote:
> I'll go back to investigating the initial report now. My current
> theory is that we need to change deb-systemd-helper so that it
> behaves more like systemctl. Once I've convinced myself further, I'll
> file a bug.
This has now b
On Sun, Oct 20, 2024 at 11:49:38AM +0200, Andrea Bolognani wrote:
> On Sat, Oct 05, 2024 at 07:51:26PM +0200, Andrea Bolognani wrote:
> > virtlogd and virtlockd are secondary daemons that the primary
> > libvirtd daemon might need to delegate some operations to, so it
> > makes sense that they'll b
On Sat, Oct 05, 2024 at 07:51:26PM +0200, Andrea Bolognani wrote:
> virtlogd and virtlockd are secondary daemons that the primary
> libvirtd daemon might need to delegate some operations to, so it
> makes sense that they'll be enabled/started together with it; at the
> same time, there are scenario
Am 06.10.24 um 18:01 schrieb Andrea Bolognani:
Sorry, I'm very confused.
Sorry for the confusion, no idea what's going wrong then.
Michael
On Sun, Oct 06, 2024 at 01:12:57PM +0200, Michael Biebl wrote:
> Am 05.10.24 um 19:51 schrieb Andrea Bolognani:
> > On Fri, Oct 04, 2024 at 08:57:36PM +0200, Michael Biebl wrote:
> > > My recommendation would be to drop the "Also=virtlockd.socket" line from
> > > libvirt.service (and "Also=virtlogd
Am 05.10.24 um 19:51 schrieb Andrea Bolognani:
On Fri, Oct 04, 2024 at 08:57:36PM +0200, Michael Biebl wrote:
On Sat, 28 Sep 2024 18:57:05 +0200 Christoph Anton Mitterer
wrote:
Upgrading the package gives:
Setting up libvirt-daemon (10.7.0-3) ...
/usr/bin/deb-systemd-helper: error: unable to
On Fri, Oct 04, 2024 at 09:10:45PM +0200, Christoph Anton Mitterer wrote:
> It would additionally be nice know *what exactly* virtlogd/virtlockd
> are needed for (and thus, whether one really needs it or not)... so
> far, I seem to run fine without virtlockd (which I haven't installed,
> after it w
On Fri, Oct 04, 2024 at 08:57:36PM +0200, Michael Biebl wrote:
> On Sat, 28 Sep 2024 18:57:05 +0200 Christoph Anton Mitterer
> wrote:
> > Upgrading the package gives:
> > Setting up libvirt-daemon (10.7.0-3) ...
> > /usr/bin/deb-systemd-helper: error: unable to read virtlockd.socket
> > Setting u
On Fri, 2024-10-04 at 20:57 +0200, Michael Biebl wrote:
> My recommendation would be to drop the "Also=virtlockd.socket" line
> from
> libvirt.service (and "Also=virtlogd.socket" as well), or upgrade the
> weak recommends to a depends for both packages.
It would additionally be nice know *what ex
On Sat, 28 Sep 2024 18:57:05 +0200 Christoph Anton Mitterer
wrote:
Package: libvirt-daemon
Version: 10.7.0-3
Severity: normal
Hey.
Upgrading the package gives:
Setting up libvirt-daemon (10.7.0-3) ...
/usr/bin/deb-systemd-helper: error: unable to read virtlockd.socket
Setting up libvirt-daemon
Package: libvirt-daemon
Version: 10.7.0-3
Severity: normal
Hey.
Upgrading the package gives:
Setting up libvirt-daemon (10.7.0-3) ...
/usr/bin/deb-systemd-helper: error: unable to read virtlockd.socket
Setting up libvirt-daemon-driver-nwfilter (10.7.0-3) ...
...
Cheers,
Chris.
-- System Inform
11 matches
Mail list logo
