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

Re: A stop job is running for...

On 12/01/2015 09:47 AM, Sven Arvidsson wrote:
On Mon, 2015-11-30 at 21:04 -0500, Jape Person wrote:
Make remote CUPS printers available locally
Network Time Synchronization

For several weeks I've been seeing this stop job notification for
two items frequently when rebooting or shutting down two of my four
testing systems.

The first notification counts all the way up to 1 min 30 sec before
shutdown scroll restarts. The second notification only counts for a
seconds before terminating.

I'm a patient guy, but adding almost two minutes to almost every
or shutdown procedure gets a bit tedious after a while.

Yes, I have noticed this too, but with different services. So it's
probably not specific to CUPS or NTP.

Unfortunately it seems to always happen when I need to shutdown quickly
(thunderstorms). Would be great if it was possible to configure the
countdown to simply kill the service after a few seconds and proceed
with shutdown/reboot.

Thanks for your response, Sven. It's nice to know that someone else has seen this type of problem. I was thinking that this could be self-inflicted. Perhaps that's a little less likely now.

So, is this behavior controlled by systemd?

I'm not trying to start a fracas. I'm really interested. What I'm asking is, do I need to start poring over systemd documentation to see if there might be a way to control this behavior?

Reply to: