Displaying 5 results from an estimated 5 matches for "defaulttimeoutstartsec".
2019 May 22
3
Bypassing 'A stop job is running' when rebooting CentOS 7
On Wed, May 22, 2019 at 09:07:32AM -0600, James Szinger wrote:
> On Wed, May 22, 2019 at 7:44 AM mark <m.roth at 5-cent.us> wrote:
> >
> > The joys of systemd....
>
> I'm not sure it's right to blame systemd. Systemd asked nicely for
> the service to shutdown.
But we can blame systemd for the cryptic message
A stop job is running
Surely systemd knows
2016 Dec 20
1
CentOS 7 and systemd: SysV initscript: how detect boot vs. interactive use?
...Wants=network-online.target.
>
>Secondly, I'd try to find a way for the auxiliary services to ping the
>prime service to ensure its up, and make that script a ExecStartPre
>entry in the [Service] section. You'll want to adjust the
>TimeoutStartSec in case it might exceed the DefaultTimeoutStartSec in
>/etc/systemd/system.conf, which is 90 seconds.
Thank you for the idea, but as mentioned, the same service runs on a mix
of server platforms and distros, and the older ones do not use systemd, so
I'd prefer to stick with SysV type initscripts that work on all of them.
2016 Dec 19
2
CentOS 7 and systemd: SysV initscript: how detect boot vs. interactive use?
James Hogarth <james.hogarth at gmail.com>
wrote:
>On 18 Dec 2016 10:59, "whitivery" <co55-sy1t at dea.spamcon.org> wrote:
>
>Moving from CentOS 5 to CentOS 7, discovered that a test in a SysV
>initscript for whether it is running interactively, instead of at boot
>time, no longer works.
>
>Under CentOS 7 / systemd, is there some way for the initscript
2016 Dec 19
0
CentOS 7 and systemd: SysV initscript: how detect boot vs. interactive use?
...[Unit] section add Wants=network-online.target.
Secondly, I'd try to find a way for the auxiliary services to ping the
prime service to ensure its up, and make that script a ExecStartPre
entry in the [Service] section. You'll want to adjust the
TimeoutStartSec in case it might exceed the DefaultTimeoutStartSec in
/etc/systemd/system.conf, which is 90 seconds.
--
Jonathan Billings <billings at negate.org>
2019 May 22
0
Bypassing 'A stop job is running' when rebooting CentOS 7
...t to blame systemd. Systemd asked nicely for
> > the service to shutdown.
>
> But we can blame systemd for the cryptic message
>
> A stop job is running
I didn't read this thread all that carefully, but has anyone mentioned
editing /etc/systemd/system.conf and changing DefaultTimeoutStartSec and
DefaultTimeoutStopSec to a lower value?
--
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6