Hi,
I'm coming here from linux-raid community. Coly proposed to remove
"Killmode=none" from our [email protected][1]. Community accepted the change
because it is reasonable, the option will removed in the future. Now when the
change is incorporated with distributions we are observing hang tasks during
will try in this way.
thanks for feedback.
regards, lacsaP.
Le ven. 20 mai 2022 à 19:38, Mike Gilbert a écrit :
> On Fri, May 20, 2022 at 1:34 PM Mike Gilbert wrote:
> >
> > On Fri, May 20, 2022 at 12:54 PM Pascal wrote:
> > >
> > > not really in the sense that qemu-nbd launches and immediate
On Fri, May 20, 2022 at 1:34 PM Mike Gilbert wrote:
>
> On Fri, May 20, 2022 at 12:54 PM Pascal wrote:
> >
> > not really in the sense that qemu-nbd launches and immediately gives the
> > hand back to the script that called it.
> > the script ends positively and qemu-nbd is killed by systemd bec
On Fri, May 20, 2022 at 12:54 PM Pascal wrote:
>
> not really in the sense that qemu-nbd launches and immediately gives the hand
> back to the script that called it.
> the script ends positively and qemu-nbd is killed by systemd because it is
> considered to be garbage left behind by the script.
not really in the sense that qemu-nbd launches and immediately gives the
hand back to the script that called it.
the script ends positively and qemu-nbd is killed by systemd because it is
considered to be garbage left behind by the script.
this is not quite the case of a timeout that systemd termin
On Fri, May 20, 2022 at 10:51 AM Pascal wrote:
> it is not strictly speaking a long-running process but it is a child who
> survives his father and who is killed when his father stops living
> successfully ! what a strange world these children live in... ;-)
Sorry, I missed this last line. Are
On Fri, May 20, 2022 at 10:51 AM Pascal wrote:
>
> hi,
>
> is it possible to influence the killmode of a script launched by an udev rule
> ?
>
> I have a udev rule that starts a script that itself starts qemu-nbd that gets
> killed once the script is finished (qemu-nbd links a block device to an
hi,
is it possible to influence the *killmode* of a script launched by an udev
rule ?
I have a udev rule that starts a script that itself starts qemu-nbd that
gets killed once the script is finished (qemu-nbd links a block device to
an nbd node).
it is not strictly speaking a *long-running proce
