From thanhdongtaylor at gmail.com  Mon Dec  4 17:22:02 2017
From: thanhdongtaylor at gmail.com (thanh dong)
Date: Mon, 4 Dec 2017 12:22:02 -0500
Subject: [Pkg-sysvinit-devel] Bug#326647: thanh dong 19652110
References: <E1EBzzB-0007i0-GS@saruman.uio.no>
Message-ID: <C85AC672-3742-44EE-B394-FB408E717D4E@gmail.com>



???c g?i t? iPhone c?a t?i

From owner at bugs.debian.org  Thu Dec 21 17:03:03 2017
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Thu, 21 Dec 2017 17:03:03 +0000
Subject: [Pkg-sysvinit-devel] Processed: affects 826214
References: <1513875591-2874-bts-myon@debian.org>
Message-ID: <handler.s.C.151387559413708.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> affects 826214 - prometheus prometheus-node-exporter
Bug #826214 [sysvinit-utils] SysV init scripts using init-d-script are not properly redirected to systemctl
Removed indication that 826214 affects prometheus and prometheus-node-exporter
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
826214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826214
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From valerie_leroy at outlook.com  Fri Dec 22 08:42:36 2017
From: valerie_leroy at outlook.com (=?UTF-8?Q?Val=C3=A9rie?= LEROY)
Date: Fri, 22 Dec 2017 08:42:36 +0000
Subject: [Pkg-sysvinit-devel] =?utf-8?q?Bug=23710343=3A_Offre_de_pr=C3=AAt?=
	=?utf-8?q?_entre_particuliers_en_72h?=
References: <87ehcpw5vg.fsf@duckcorp.org>
Message-ID: <DB3PR05MB08411B0654286457468C16018E020@DB3PR05MB0841.eurprd05.prod.outlook.com>

Bonjour a vous Mr /Mme

Vous ?tes ? la recherche de pr?t pour soit relancer vos activit?s soit pour la r?alisation d'un projet , soit pour vous acheter un appartement mais vous ?tes interdit bancaire ou votre dossier ? ?t? rejet? ? la banque. Je suis un particulier j?octroie des pr?ts allant de 4000? ? 7.000.000? ? toutes personnes capable de respecter les conditions . Mon taux d?int?r?t est de 2% . Si vous avez besoin d'argent pour d'autres raisons , n?h?sitez pas ? me contacter pour plus d'informations. particuliers s?rieux et honn?tes.
Contactez-nous pour plus d'informations.

Courriel : argent_rapide at outlook.com

Courriel : argent_rapide at outlook.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20171222/09672409/attachment.html>

From owner at bugs.debian.org  Mon Dec 25 22:24:02 2017
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 25 Dec 2017 22:24:02 +0000
Subject: [Pkg-sysvinit-devel] Bug#706877: marked as done (insserv: breaks
 dist-upgrade by installing before packages fix their init scripts)
References: <20171225222208.6rov36oagrusulxr@angband.pl>
 <20130505174624.31576.93691.reportbug@localhost.localdomain>
Message-ID: <handler.706877.D706877.151424053124403.ackdone@bugs.debian.org>

Your message dated Mon, 25 Dec 2017 23:22:08 +0100
with message-id <20171225222208.6rov36oagrusulxr at angband.pl>
and subject line upgrades _to_ wheezy are not interesting anymore
has caused the Debian Bug report #706877,
regarding insserv: breaks dist-upgrade by installing before packages fix their init scripts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
706877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706877
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Jamin Collins <jcollins at asgardsrealm.net>
Subject: insserv: breaks dist-upgrade by installing before packages fix their init scripts
Date: Sun, 05 May 2013 11:46:24 -0600
Size: 3440
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20171225/fd58020d/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Adam Borowski <kilobyte at angband.pl>
Subject: upgrades _to_ wheezy are not interesting anymore
Date: Mon, 25 Dec 2017 23:22:08 +0100
Size: 2250
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20171225/fd58020d/attachment-0001.mht>

From kilobyte at angband.pl  Tue Dec 26 11:35:13 2017
From: kilobyte at angband.pl (Adam Borowski)
Date: Tue, 26 Dec 2017 12:35:13 +0100
Subject: [Pkg-sysvinit-devel] Bug#872039: why the severity?
References: <20170813174635.GA32314@Ahorn.local>
Message-ID: <20171226113513.wkba2epjw37xjhld@angband.pl>

> Reason for Severity=serious: This leaves /var (or other
> filesystems) in an unclean state, so could possibly lead to
> data loss!

Please tell me why this would be serious: any filesystem from this millenium
can handle unclean shutdown fine -- especially if there's a sync before
reboot/poweroff.

For example, on my desktop, non-trivial subvolume layout leads to:

[ ok ] Unmounting temporary filesystems...done.
[ ok ] Deactivating swap...done.
[....] Unmounting weak filesystems...umount: /srv/chroots/tmp/home: target is busy.
umount: /srv/chroots: target is busy.
umount: /home: target is busy.
failed.
[ ok ] Unmounting local filesystems...done.
[16396.379093] BTRFS info (device sda1): using free space tree
[ ok ] Stopping the hotplug events dispatcher: systemd-udevd.
[info] Will now halt.
[16399.026813] kvm: exiting hardware virtualization
[16399.031944] sd 2:0:0:0: [sdb] Synchronizing SCSI cache
[16399.037624] sd 2:0:0:0: [sdb] Stopping disk
[16400.789927] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[16400.798161] sd 0:0:0:0: [sda] Stopping disk
[16402.943670] ACPI: Preparing to enter system sleep state S5
[16403.045314] reboot: Power down

Which I did not bother to look into for many years, yet there's never been
any data loss.  A sudden _unexpected_ failure (such as due to power
blackout, PSU being flaky, etc) may lead to losing contents of files written
seconds before the failure, but if the filesystem itself needs a fsck,
please report a serious bug against the filesystem in question (yeah,
they're parts of the kernel rather than individual Debian packages, but
you know where to find their maintainers).  An orderly shutdown that doesn't
fully unmount a filesystem doesn't count as unexpected.

Fixing this bug in general is not really possible, as enumerating some
namespaces may be not trivial, processes might be stuck in D state due to
some bug, etc.  Thus, a sync is supposed to be enough.

Filesystems that can't take unclean shutdown do exist (vfat, ext2), but no
one seriously considers running a system from them -- and a sync with no
further writes means no data loss either.


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.


From jsmith at resonatingmedia.com  Mon Dec 25 02:07:53 2017
From: jsmith at resonatingmedia.com (Jesse Smith)
Date: Sun, 24 Dec 2017 22:07:53 -0400
Subject: [Pkg-sysvinit-devel] SysV init upstream work
Message-ID: <4ff655e7-4115-acff-aece-68122705aab0@resonatingmedia.com>

Hello Debian init developers,

I am doing some work on the upstream SysV init code, cleaning things up
and upstreaming patches. If you have any Debian-specific patches for
init that you'd like to get passed upstream, please let me know. Or post
to the SysV mailing list and I'll pick them up from there.

Best wishes,
Jesse


From dpovey at gmail.com  Sat Dec 30 23:07:15 2017
From: dpovey at gmail.com (Daniel Povey)
Date: Sat, 30 Dec 2017 15:07:15 -0800
Subject: [Pkg-sysvinit-devel] Bug#719273: Acknowledgement (sysvinit-utils:
	/bin/pidof fails when there are stuck NFS mount points,
	preventing shutdown)
In-Reply-To: <CAEWAuyRh+D_XBhY7xczHFoHnr7yCWSLqPM5C6ALADphKaivyJQ@mail.gmail.com>
References: <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
 <handler.719273.B.13760910493694.ack@bugs.debian.org>
 <CAEWAuyRh+D_XBhY7xczHFoHnr7yCWSLqPM5C6ALADphKaivyJQ@mail.gmail.com>
 <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
Message-ID: <CAEWAuySytVmbrahxyvgk9E3p4amv-QpBZowfmXX=UCRCoOZA5g@mail.gmail.com>

Guys,

No-one ever responded to this thread (years ago).
We have just noticed the same problem on a newer version of Debian and we
are going to dig up our old patch and use it.
This is an issue for services like rpcbind for which systemd uses the older
SysV init scripts.

Dan


On Sat, Aug 10, 2013 at 2:11 PM, Daniel Povey <dpovey at gmail.com> wrote:

> I am sending a patch to the source of "killall5" that I am using
> locally.  It basically ignores all processes in a "D" or "Z" state (or
> states where D or Z appear in the string).  This is of course not
> ideal, but it works for me.  I found that not all machines where I had
> stuck processes, would cause problems for start-stop-daemon-- this
> patch is only for "pidof".  I may later replicate the problem with
> start-stop-daemon and figure out a fix.
>
>
> root at a04:~# diff -c sysvinit-2.88dsf/src/killall5.c
> sysvinit-2.88dsf-modified/src/killall5.c
> *** sysvinit-2.88dsf/src/killall5.c     Sat Aug 10 17:05:31 2013
> --- sysvinit-2.88dsf-modified/src/killall5.c    Sat Aug 10 16:50:27 2013
> ***************
> *** 1,5 ****
>   /*
> !  * kilall5.c  Kill all processes except processes that have the
>    *            same session id, so that the shell that called us
>    *            won't be killed. Typically used in shutdown scripts.
>    *
> --- 1,5 ----
>   /*
> !  * killall5.c Kill all processes except processes that have the
>    *            same session id, so that the shell that called us
>    *            won't be killed. Typically used in shutdown scripts.
>    *
> ***************
> *** 536,548 ****
>                         p->statname = (char *)xmalloc(strlen(s)+1);
>                         strcpy(p->statname, s);
>
>                         /* Get session, startcode, endcode. */
>                         startcode = endcode = 0;
> !                       if (sscanf(q,   "%*c %*d %*d %d %*d %*d %*u %*u "
>                                         "%*u %*u %*u %*u %*u %*d %*d "
>                                         "%*d %*d %*d %*d %*u %*u %*d "
>                                         "%*u %lu %lu",
> !                                       &p->sid, &startcode, &endcode) !=
> 3) {
>                                 p->sid = 0;
>                                 nsyslog(LOG_ERR, "can't read sid from
> %s\n",
>                                         path);
> --- 536,550 ----
>                         p->statname = (char *)xmalloc(strlen(s)+1);
>                         strcpy(p->statname, s);
>
> +                       char status[11];
> +
>                         /* Get session, startcode, endcode. */
>                         startcode = endcode = 0;
> !                       if (sscanf(q,   "%10s %*d %*d %d %*d %*d %*u %*u "
>                                         "%*u %*u %*u %*u %*u %*d %*d "
>                                         "%*d %*d %*d %*d %*u %*u %*d "
>                                         "%*u %lu %lu",
> !                                       status, &p->sid, &startcode,
> &endcode) != 4) {
>                                 p->sid = 0;
>                                 nsyslog(LOG_ERR, "can't read sid from
> %s\n",
>                                         path);
> ***************
> *** 555,560 ****
> --- 557,571 ----
>                         if (startcode == 0 && endcode == 0)
>                                 p->kernel = 1;
>                         fclose(fp);
> +                       if (strchr(status, 'D') != NULL ||
> strchr(status, 'Z') != NULL) {
> +                         /* Ignore zombie processes or processes in
> disk sleep, as attempts
> +                            to access the stats of these will
> sometimes fail. */
> +                         if (p->argv0) free(p->argv0);
> +                         if (p->argv1) free(p->argv1);
> +                         if (p->statname) free(p->statname);
> +                         free(p);
> +                         continue;
> +                       }
>                 } else {
>                         /* Process disappeared.. */
>                         if (p->argv0) free(p->argv0);
>
>
>
>
> On Fri, Aug 9, 2013 at 7:33 PM, Debian Bug Tracking System
> <owner at bugs.debian.org> wrote:
> > Thank you for filing a new Bug report with Debian.
> >
> > This is an automatically generated reply to let you know your message
> > has been received.
> >
> > Your message is being forwarded to the package maintainers and other
> > interested parties for their attention; they will reply in due course.
> >
> > Your message has been sent to the package maintainer(s):
> >  Debian sysvinit maintainers <pkg-sysvinit-devel at lists.alioth.debian.org
> >
> >
> > If you wish to submit further information on this problem, please
> > send it to 719273 at bugs.debian.org.
> >
> > Please do not send mail to owner at bugs.debian.org unless you wish
> > to report a problem with the Bug-tracking system.
> >
> > --
> > 719273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719273
> > Debian Bug Tracking System
> > Contact owner at bugs.debian.org with problems
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20171230/80890c61/attachment.html>

From owner at bugs.debian.org  Sat Dec 30 23:24:03 2017
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 30 Dec 2017 23:24:03 +0000
Subject: [Pkg-sysvinit-devel] Processed: Re: Bug#719273: Acknowledgement
 (sysvinit-utils: /bin/pidof fails when there are stuck NFS mount points,
 preventing shutdown)
References: <23112.7974.857944.798662@chiark.greenend.org.uk>
 <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
Message-ID: <handler.s.B719273.151467601120054.transcript@bugs.debian.org>

Processing control commands:

> tags -1 + patch
Bug #719273 [sysvinit-utils] sysvinit-utils: /bin/pidof fails when there are stuck NFS mount points, preventing shutdown
Added tag(s) patch.

-- 
719273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719273
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ijackson at chiark.greenend.org.uk  Sat Dec 30 23:20:06 2017
From: ijackson at chiark.greenend.org.uk (Ian Jackson)
Date: Sat, 30 Dec 2017 23:20:06 +0000
Subject: [Pkg-sysvinit-devel] Bug#719273: Acknowledgement (sysvinit-utils:
	/bin/pidof fails when there are stuck NFS mount points,
	preventing shutdown)
In-Reply-To: <CAEWAuySytVmbrahxyvgk9E3p4amv-QpBZowfmXX=UCRCoOZA5g@mail.gmail.com>
References: <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
 <handler.719273.B.13760910493694.ack@bugs.debian.org>
 <CAEWAuyRh+D_XBhY7xczHFoHnr7yCWSLqPM5C6ALADphKaivyJQ@mail.gmail.com>
 <CAEWAuySytVmbrahxyvgk9E3p4amv-QpBZowfmXX=UCRCoOZA5g@mail.gmail.com>
 <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
Message-ID: <23112.7974.857944.798662@chiark.greenend.org.uk>

Control: tags -1 + patch

Daniel Povey writes ("Bug#719273: Acknowledgement (sysvinit-utils: /bin/pidof fails when there are stuck NFS mount points, preventing shutdown)"):
> No-one ever responded to this thread (years ago).
> We have just noticed the same problem on a newer version of Debian and we are
> going to dig up our old patch and use it.
> This is an issue for services like rpcbind for which systemd uses the older
> SysV init scripts.  

Thanks for pinging this bug.

Do you know if the patch still applies to current sysvinit source ?

Reading a non-unified diff certainly takes me back some years...

Regards,
Ian.


From dpovey at gmail.com  Sat Dec 30 23:23:53 2017
From: dpovey at gmail.com (Daniel Povey)
Date: Sat, 30 Dec 2017 15:23:53 -0800
Subject: [Pkg-sysvinit-devel] Bug#719273: Acknowledgement (sysvinit-utils:
	/bin/pidof fails when there are stuck NFS mount points,
	preventing shutdown)
In-Reply-To: <23112.7974.857944.798662@chiark.greenend.org.uk>
References: <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
 <handler.719273.B.13760910493694.ack@bugs.debian.org>
 <CAEWAuyRh+D_XBhY7xczHFoHnr7yCWSLqPM5C6ALADphKaivyJQ@mail.gmail.com>
 <CAEWAuySytVmbrahxyvgk9E3p4amv-QpBZowfmXX=UCRCoOZA5g@mail.gmail.com>
 <23112.7974.857944.798662@chiark.greenend.org.uk>
 <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
Message-ID: <CAEWAuyRUJcnDjk48XjtkwP0Q3jh+1Mi1qyk0wwV51yrPizKOCQ@mail.gmail.com>

We're going to check it out early next week, whether it still applies.

The bug it fixes is a situation where pidof reaches a process that's in a
bad state such as D or Z, that might have an executable on a stuck mount
point or something like that, and gets stuck, preventing system maintenance
tasks or shutdown.





On Sat, Dec 30, 2017 at 3:20 PM, Ian Jackson <
ijackson at chiark.greenend.org.uk> wrote:

> Control: tags -1 + patch
>
> Daniel Povey writes ("Bug#719273: Acknowledgement (sysvinit-utils:
> /bin/pidof fails when there are stuck NFS mount points, preventing
> shutdown)"):
> > No-one ever responded to this thread (years ago).
> > We have just noticed the same problem on a newer version of Debian and
> we are
> > going to dig up our old patch and use it.
> > This is an issue for services like rpcbind for which systemd uses the
> older
> > SysV init scripts.
>
> Thanks for pinging this bug.
>
> Do you know if the patch still applies to current sysvinit source ?
>
> Reading a non-unified diff certainly takes me back some years...
>
> Regards,
> Ian.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20171230/a9dbb64d/attachment-0001.html>

From pere at hungry.com  Sun Dec 31 14:49:16 2017
From: pere at hungry.com (Petter Reinholdtsen)
Date: Sun, 31 Dec 2017 15:49:16 +0100
Subject: [Pkg-sysvinit-devel] Bug#719273: sysvinit-utils: /bin/pidof fails
	when there are stuck NFS mount points, preventing shutdown
In-Reply-To: <CAEWAuyRUJcnDjk48XjtkwP0Q3jh+1Mi1qyk0wwV51yrPizKOCQ@mail.gmail.com>
References: <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
 <handler.719273.B.13760910493694.ack@bugs.debian.org>
 <CAEWAuyRh+D_XBhY7xczHFoHnr7yCWSLqPM5C6ALADphKaivyJQ@mail.gmail.com>
 <CAEWAuySytVmbrahxyvgk9E3p4amv-QpBZowfmXX=UCRCoOZA5g@mail.gmail.com>
 <23112.7974.857944.798662@chiark.greenend.org.uk>
 <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
 <CAEWAuyRUJcnDjk48XjtkwP0Q3jh+1Mi1qyk0wwV51yrPizKOCQ@mail.gmail.com>
 <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
Message-ID: <2fllghjrlzn.fsf@diskless.uio.no>

pDaniel Povey]
> We're going to check it out early next week, whether it still applies.
>
> The bug it fixes is a situation where pidof reaches a process that's in a
> bad state such as D or Z, that might have an executable on a stuck mount
> point or something like that, and gets stuck, preventing system maintenance
> tasks or shutdown.

Perhaps something to send upstream,
<URL: https://savannah.nongnu.org/projects/sysvinit/ >?   Someone
recently showed up on the upstream mailing list and offered to update
upstream source. :)

-- 
Happy hacking
Petter Reinholdtsen


From ijackson at chiark.greenend.org.uk  Sun Dec 31 17:31:20 2017
From: ijackson at chiark.greenend.org.uk (Ian Jackson)
Date: Sun, 31 Dec 2017 17:31:20 +0000
Subject: [Pkg-sysvinit-devel] Bug#719273: Acknowledgement (sysvinit-utils:
	/bin/pidof fails when there are stuck NFS mount points,
	preventing shutdown)
In-Reply-To: <CAEWAuyRUJcnDjk48XjtkwP0Q3jh+1Mi1qyk0wwV51yrPizKOCQ@mail.gmail.com>
References: <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
 <handler.719273.B.13760910493694.ack@bugs.debian.org>
 <CAEWAuyRh+D_XBhY7xczHFoHnr7yCWSLqPM5C6ALADphKaivyJQ@mail.gmail.com>
 <CAEWAuySytVmbrahxyvgk9E3p4amv-QpBZowfmXX=UCRCoOZA5g@mail.gmail.com>
 <23112.7974.857944.798662@chiark.greenend.org.uk>
 <CAEWAuyRUJcnDjk48XjtkwP0Q3jh+1Mi1qyk0wwV51yrPizKOCQ@mail.gmail.com>
 <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
Message-ID: <23113.7912.968054.616902@chiark.greenend.org.uk>

Daniel Povey writes ("Bug#719273: Acknowledgement (sysvinit-utils: /bin/pidof fails when there are stuck NFS mount points, preventing shutdown)"):
> We're going to check it out early next week, whether it still applies.
> 
> The bug it fixes is a situation where pidof reaches a process that's in a bad
> state such as D or Z, that might have an executable on a stuck mount point or
> something like that, and gets stuck, preventing system maintenance tasks or
> shutdown.

Yes.  The principle of the patch LGTM.  Hence my tagging the bug
accordingly.

Thanks for your persistence.

Ian.


From dpovey at gmail.com  Sun Dec 31 19:39:07 2017
From: dpovey at gmail.com (Daniel Povey)
Date: Sun, 31 Dec 2017 11:39:07 -0800
Subject: [Pkg-sysvinit-devel] Bug#719273: Acknowledgement (sysvinit-utils:
	/bin/pidof fails when there are stuck NFS mount points,
	preventing shutdown)
In-Reply-To: <23113.7912.968054.616902@chiark.greenend.org.uk>
References: <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
 <handler.719273.B.13760910493694.ack@bugs.debian.org>
 <CAEWAuyRh+D_XBhY7xczHFoHnr7yCWSLqPM5C6ALADphKaivyJQ@mail.gmail.com>
 <CAEWAuySytVmbrahxyvgk9E3p4amv-QpBZowfmXX=UCRCoOZA5g@mail.gmail.com>
 <23112.7974.857944.798662@chiark.greenend.org.uk>
 <CAEWAuyRUJcnDjk48XjtkwP0Q3jh+1Mi1qyk0wwV51yrPizKOCQ@mail.gmail.com>
 <23113.7912.968054.616902@chiark.greenend.org.uk>
 <20130809225213.24325.72655.reportbug@a01.clsp.jhu.edu>
Message-ID: <CAEWAuyQgDv-5uHpq9G8wXv8CQ_jG2r9FYhz4X50XOE8nz=1sQQ@mail.gmail.com>

Guys, I just want to give a bit more context that I've found out since then
which might be relevant.

As you probably know (but to document it here), if you set the variable
PIDOF_NETFS or set the flag -n for 'pidof', it will avoid trying to stat
files on NFS partitions.  This will solve some of these types of issues--
but not all of them, because a binary that's local can still be in D state
due to accessing a stuck partition.  I'd also like to point out (and I
don't know if this is really the case but it might be) that maybe a process
that's not in a D or Z state might still have a binary on a stuck mount
point where calling "stat" on it would fail.  But I don't want to
complicate things too much: a partial fix is better than nothing.

Also, at the current time (and IIRC this wasn't the case when we submitted
the original patch), start-stop-daemon is a binary not a script, and it
doesn't call pidof or killall.  Instead it uses its own code, and that code
is subject to the same issue where it hangs on stuck NFS partitions.
Therefore, as it stands, applying this patch to 'pidof' will no longer
resolve the issue; similar changes would have to be made to 'killall'.

We have a cluster of Linux servers running GridEngine, and they each export
volumes via NFS.  We have a problem when one of the NFS servers dies.  The
stuck mount point on other nodes causes user processes there to enter the D
state (e.g. if they have pending output to the disk that's down).  This
makes it impossible to do routine maintenance on the other nodes, so they
pretty soon will need a reboot, and very often in this condition those
reboots will fail because a shutdown task hangs.  Their unavailable NFS
volumes cause failures on other nodes in turn, unless someone is available
to physically reboot.  (We're planning to eventually use virtualization to
prevent this failure; previously there were complications relating to
NVidia GPUs).

Dan



On Sun, Dec 31, 2017 at 9:31 AM, Ian Jackson <
ijackson at chiark.greenend.org.uk> wrote:

> Daniel Povey writes ("Bug#719273: Acknowledgement (sysvinit-utils:
> /bin/pidof fails when there are stuck NFS mount points, preventing
> shutdown)"):
> > We're going to check it out early next week, whether it still applies.
> >
> > The bug it fixes is a situation where pidof reaches a process that's in
> a bad
> > state such as D or Z, that might have an executable on a stuck mount
> point or
> > something like that, and gets stuck, preventing system maintenance tasks
> or
> > shutdown.
>
> Yes.  The principle of the patch LGTM.  Hence my tagging the bug
> accordingly.
>
> Thanks for your persistence.
>
> Ian.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20171231/07d138cd/attachment.html>