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

Re: A stop job is running for...

On Wednesday 02 December 2015 06:06:09 Martin Read wrote:

> On 02/12/15 03:07, James P. Wallen wrote:
> > 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?
> If a stop job is taking two minutes, that suggests that the service
> has one or more ExecStop lines defined in its service unit and that
> one of those commands is taking an unduly long time to complete for
> some reason.
> The default and per-service timeout values for stopping a service
> (after which systemd gives up and sends fatal signals to all of the
> service's processes) are configurable; see the systemd-system.conf(5)
> and systemd.service(5) man pages for details.

'scuse me, but shouldn't the errant process be fixed so it can stop and 
clean up after itself?  Thats the real bug here.

Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Reply to: