trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: July 2018

Re: [trinity-users] a stop job is running for Trinity Display Manager (xxx/1min30sec)

From: Felix Miata <mrmazda@...>
Date: Tue, 24 Jul 2018 16:31:23 -0400
Felix Miata composed on 2018-07-23 22:23 (UTC-0400):

> Michele Calgaro composed on 2018-07-20 10:16 (UTC+0800):

>>> Reduce the timeout of exactly what/where? This happens with the openSUSEes and the
>>> Debians./etc/systemd/system.comf

>> Uncomment and change like this:
>> DefaultTimeoutStartSec=5s
>> DefaultTimeoutStopSec=5s
>> This should reduce the wait time to 5 seconds.

> Bad idea. This system has no SDD. I did exactly that, and bunches of startup
> units failed

> 	# journalctl -b -1 | grep ailed | wc -l
> 	14

> among which local-fs.target/start, leaving me in emergency mode.
> I switched Start to 15 and it seems to have booted normally, even though

> 	# journalctl -b | grep ailed | wc -l

> returned 12. I switched it to 75, and still got 12. So I switched it back
> to its original 90, and it still got 12. So I switched back to 5. Next boot
> produced 15, but all seemed totally normal.

> Oh what fun is systemd. :-p

> (but no reboot/shutdown delays since playing with system.conf either)

Spoke too soon. It just sat there 90 seconds reporting "watchdog did not stop!"
before it rebooted.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/