Re: A stop job is running for...

[Jape Person <japers@comcast.net>]

On 12/02/2015 12:17 PM, Michael Biebl wrote:
> Am 02.12.2015 um 18:05 schrieb Jape Person:
> > On 12/02/2015 10:49 AM, David Wright wrote:
> > > I have observed behaviour where, when the time limit of 90 seconds is
> > > reached, the limit increases by another 90 seconds and nothing else
> > > happens (for hours). eg
> > >
> > > [ <*> ] A stop job is running for Manage, Install and Generate Color
> > > Profiles (34min 54s / 36min)_
> > >
> > > Fortunately, that hasn't happened for a few months. It's very
> > > embarrassing when my laptop takes longer to close down than my
> > > wife's W10.
>
> Sounds like it could be hard to reproduce indeed.
>
> > Now *that* would be annoying.
>
> In case you run into such a situation again, where a service is blocking
> the shutdown you can of course just use force and pull the plug or use
> sysrq b.
> But there is a nicer alternative: just hit ctrl+alt+del quickly 7 times.
> systemd then will initiate a forced shutdown. See [1].
>
> Regards,
> Michael
>
>
> http://www.freedesktop.org/software/systemd/man/systemd.html#SIGINT

Seven times. How lucky!

Heh.

Thank you, Michael.

Do you think it's better just force the shutdown than to rummage around 
in the service unit files? I'm loath to edit system configuration files 
unless it's to configure something like smartmontools or some such -- 
you know, something that is more ordinarily edited in order to get it to 
do some specific job.

I guess that argument could apply to service units, but I'm not used to 
this stuff, yet.

Thanks again,
JP