[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: A stop job is running for...

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

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.



(1) https://bugzilla.redhat.com/show_bug.cgi?id=1044602

Reply to: