Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #161485
| From | Jape Person <japers@comcast.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: A stop job is running for... |
| Date | 2015-12-03 00:40 +0100 |
| Message-ID | <qBpaa-5uf-13@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <qB6qS-1LU-1@gated-at.bofh.it> <qBdsn-6oc-31@gated-at.bofh.it> <qBkka-2qa-9@gated-at.bofh.it> <qBkWR-2Tg-1@gated-at.bofh.it> <qBoxs-50H-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 12/02/2015 05:59 PM, Don Armstrong wrote: > On Wed, 02 Dec 2015, Jape Person wrote: >> It's occurred to me that, though I have occasionally seen service >> shutown issues with sysv-init, they were never as pervasive or >> repetitve as it has been since switching to systemd as the init >> system. > > This is generally because sysv-init tends to not pay attention to > whether a particular service has actually stopped. Many init scripts > just send an appropriate signal, hope for the best, and return control. > Yes, that was my understanding. Sysv-init worked just fine for my my use cases, but I can easily see that the arrangement might not work so well for something like, say, a print server. > If your goal is just to shutdown the system regardless of what is > actually going on, that's great... but if you value your data, that's > not really a workable solution. > > That said, most of these cases are bugs, not really cases where the > daemon is actually doing something; reporting the bugs when you run into > them will help them get fixed. > I finally found this older thread(1) which gave me some ideas as to how to proceed in trying to find the cause of the issue. I want to be useful, but it takes a bit of time for those of us who fumble about in darkness to find the walls. We have to find one of those before we stand a chance of getting to the cave entrance. I may return if I don't first impale myself on a stalagmite. ;-) JP (1) https://bugzilla.redhat.com/show_bug.cgi?id=1044602
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-01 03:20 +0100
Re: A stop job is running for... Sven Arvidsson <sa@whiz.se> - 2015-12-01 15:50 +0100
Re: A stop job is running for... "James P. Wallen" <jpwallen@comcast.net> - 2015-12-02 04:40 +0100
Re: A stop job is running for... Martin Read <zen75502@zen.co.uk> - 2015-12-02 12:10 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-02 16:20 +0100
Re: A stop job is running for... "James P. Wallen" <jpwallen@comcast.net> - 2015-12-02 16:20 +0100
Re: A stop job is running for... Himanshu Shekhar <irm2015006@iiita.ac.in> - 2015-12-03 11:30 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-03 18:20 +0100
Re: A stop job is running for... Michael Biebl <biebl@debian.org> - 2015-12-03 19:10 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-03 21:30 +0100
Re: A stop job is running for... Michael Biebl <biebl@debian.org> - 2015-12-03 22:10 +0100
Systemd debugging (was ... Re: A stop job is running for...) Chris Bannister <cbannister@slingshot.co.nz> - 2015-12-04 10:20 +0100
Re: A stop job is running for... Rick Thomas <rbthomas@pobox.com> - 2015-12-03 19:30 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-03 22:20 +0100
Re: A stop job is running for... David Wright <deblis@lionunicorn.co.uk> - 2015-12-02 17:00 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-02 18:10 +0100
Re: A stop job is running for... Michael Biebl <biebl@debian.org> - 2015-12-02 18:20 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-02 19:00 +0100
Re: A stop job is running for... Michael Biebl <biebl@debian.org> - 2015-12-02 20:10 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-02 20:30 +0100
Re: A stop job is running for... David Wright <deblis@lionunicorn.co.uk> - 2015-12-06 03:30 +0100
Re: A stop job is running for... Gene Heskett <gheskett@shentel.net> - 2015-12-02 19:30 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-02 20:10 +0100
Re: A stop job is running for... Don Armstrong <don@debian.org> - 2015-12-03 00:00 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-03 00:40 +0100
Re: A stop job is running for... David Wright <deblis@lionunicorn.co.uk> - 2015-12-03 20:20 +0100
Re: A stop job is running for... Don Armstrong <don@debian.org> - 2015-12-04 19:50 +0100
Re: A stop job is running for... Himanshu Shekhar <irm2015006@iiita.ac.in> - 2015-12-05 07:30 +0100
Re: A stop job is running for... Jape Person <japers@comcast.net> - 2015-12-05 17:10 +0100
Re: A stop job is running for... Gene Heskett <gheskett@shentel.net> - 2015-12-03 02:20 +0100
Re: A stop job is running for... Chris Bannister <cbannister@slingshot.co.nz> - 2015-12-03 03:50 +0100
Re: A stop job is running for... "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu> - 2015-12-03 04:10 +0100
Re: A stop job is running for... Gene Heskett <gheskett@shentel.net> - 2015-12-03 04:30 +0100
Re: A stop job is running for... Gene Heskett <gheskett@shentel.net> - 2015-12-03 04:30 +0100
Re: A stop job is running for... Nicolas George <george@nsup.org> - 2015-12-03 08:50 +0100
Re: A stop job is running for... Gene Heskett <gheskett@shentel.net> - 2015-12-03 12:00 +0100
Re: A stop job is running for... <tomas@tuxteam.de> - 2015-12-03 13:10 +0100
csiph-web