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

Re: systemd fails to poweroff - "A stop job is running for Session 2 of user $USER"



On Wed, Aug 13, 2014 at 11:15:22AM +1000, Zenaan Harkness wrote:
> On 8/13/14, Paul E Condon <pecondon@mesanetworks.net> wrote:
> > I interpret the quoted string in the Subject: header as being flawed
> > use of English language. 'stop' should be 'stopped'. And, there is a
> 
> That would definitely be clearer.
> 
> I was interpreting it as some special systemd shutdown-ey thing which
> runs around trying to stop things, and that there might be various of
> these, and one of them has a problem.

Yes, I believe this is the correct interpretation. SystemD will tell all
services  to "stop".  It will  then wait  until all  those sevices  have
stopped. Some  services will  stop immediately, but  some need  a little
longer to  flush logs, finish servicing  a request or whatever.  After a
period of seconds, it appears that SystemD  will pop up a message to the
effect  of "I'm  still  here,  still responding.  I'm  just waiting  for
service X to tell me it has stopped." Given what was said earlier in the
thread, I  suspect this will  continue for  90 seconds until  it finally
gives up waiting.

> 
> I.e. "stop job" being a noun.

"Stop Command",  perhaps? "Stop-Service  command" would be  even clearer
(though  that  literal  command   doesn't  exist).  Perhaps  a  complete
rewording to "Still waiting for Service  $FOO in Session 2 of User $USER
to stop" would be clearest.

Attachment: signature.asc
Description: Digital signature


Reply to: