Hi,
On Thu, 2 Apr 2020 13:10:13 +0200 Michael Biebl wrote:
> Am 02.04.20 um 12:45 schrieb Christian Ehrhardt:
> > On Thu, Apr 2, 2020 at 10:54 AM Michael Biebl wrote:
> >>
> >> I don't think this is going to work.
> >>
> >> You'll need to restart both the service and socket in the correct order,
Am 02.04.20 um 13:09 schrieb Guido Günther:
> See 955542 , we can't get the order right with the current Also= parsing
> it seems. I'm also not sure if it's correct that Also= units are being
> restarted as well.
Also= should only have an effect when enabling a service, not when
(re)starting a se
On Thu, Apr 2, 2020, 04:53 Guido Günther wrote:
> control: reassign -1 systemd
> control: retitle -1 systemd fails to restart socket unit of already
> running service
>
> Dear systemd maintainers
> On Wed, Apr 01, 2020 at 03:52:35PM +0200, Christian Ehrhardt wrote:
> > Thanks, from that POV it ma
Hi,
On Thu, Apr 02, 2020 at 12:45:00PM +0200, Christian Ehrhardt wrote:
> On Thu, Apr 2, 2020 at 10:54 AM Michael Biebl wrote:
> >
> > I don't think this is going to work.
> >
> > You'll need to restart both the service and socket in the correct order,
>
> @Michael:
> I have tried "systemctl rest
Am 02.04.20 um 12:45 schrieb Christian Ehrhardt:
> On Thu, Apr 2, 2020 at 10:54 AM Michael Biebl wrote:
>>
>> I don't think this is going to work.
>>
>> You'll need to restart both the service and socket in the correct order,
>
> @Michael:
> I have tried "systemctl restart service socket socket"
On Thu, Apr 2, 2020 at 10:54 AM Michael Biebl wrote:
>
> I don't think this is going to work.
>
> You'll need to restart both the service and socket in the correct order,
@Michael:
I have tried "systemctl restart service socket socket" before and it works.
But I was wondering if it might work jus
Am 02.04.20 um 10:50 schrieb Michael Biebl:
> I don't think this is going to work.
>
> You'll need to restart both the service and socket in the correct order,
> i.e.
>
>
>
> systemctl restart libvirtd.service libvirtd.socket
>
Remember that a systemctl stop foo.socket will tear down the sock
I don't think this is going to work.
You'll need to restart both the service and socket in the correct order,
i.e.
systemctl restart libvirtd.service libvirtd.socket
signature.asc
Description: OpenPGP digital signature
Hi,
On Thu, Apr 02, 2020 at 10:18:53AM +0200, Michael Biebl wrote:
> Control: tags -1 + moreinfo unreproducible
>
> Am 02.04.20 um 09:52 schrieb Guido Günther:
> > control: reassign -1 systemd
> > control: retitle -1 systemd fails to restart socket unit of already running
> > service
>
you have:
Control: tags -1 + moreinfo unreproducible
Am 02.04.20 um 09:52 schrieb Guido Günther:
> control: reassign -1 systemd
> control: retitle -1 systemd fails to restart socket unit of already running
> service
root@pluto:~# systemctl status libvirtd.service libvirtd.socket
● libvirtd.service - Virt
control: reassign -1 systemd
control: retitle -1 systemd fails to restart socket unit of already running
service
Dear systemd maintainers
On Wed, Apr 01, 2020 at 03:52:35PM +0200, Christian Ehrhardt wrote:
> Thanks, from that POV it makes sense.
> I'm not good at re-assigning debian bugs could on
> > > Does that make sense?
> >
> > Almost :-)
> > Hi Guido,
> >
> > I like to summarize this from another POV:
> > - services can start and restart no matter what state the .socket files are
> > in
> > - sockets can start if the service isn't up yet
> > - sockets can start if the service is and t
Hi,
On Wed, Apr 01, 2020 at 03:21:57PM +0200, Christian Ehrhardt wrote:
> > So the problem seems to be that systemd prints that warning whenever you
> > try to restart a socket activated service that is already active and also
> > backed by a .service unit - and it doesn't matter whether it's activ
> So the problem seems to be that systemd prints that warning whenever you
> try to restart a socket activated service that is already active and also
> backed by a .service unit - and it doesn't matter whether it's activated
> by socket or via the service file).
>
> Does that make sense?
Almost :
Hi Christian,
On Wed, Apr 01, 2020 at 01:27:54PM +0200, Christian Ehrhardt wrote:
> Package: debhelper
> Version: 12.10
> X-Debbugs-CC: a...@sigxcpu.org
>
> Hi,
> I've seen this in package libvirt in Ubuntu as well as Debian, but it
> might be more widespread without me being aware of it. If we i
Package: debhelper
Version: 12.10
X-Debbugs-CC: a...@sigxcpu.org
Hi,
I've seen this in package libvirt in Ubuntu as well as Debian, but it
might be more widespread without me being aware of it. If we install
the package all is fine, but on a --reinstall or upgrade it will show
warnings about serv
16 matches
Mail list logo
