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: "Dr. Nikolaus Klepp" <office@...>
Date: Tue, 24 Jul 2018 10:10:52 +0200
Am Dienstag, 24. Juli 2018 schrieb Felix Miata:
> 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

Oh well ... have you seen this?
English: https://translate.google.de/translate?sl=de&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=http%3A%2F%2Fwww.danisch.de%2Fblog%2F2018%2F07%2F10%2Fsystemd-war-eine-massive-fehlentscheidung%2F&edit-text=&act=url
Deutsch: http://www.danisch.de/blog/2018/07/10/systemd-war-eine-massive-fehlentscheidung/

Nik

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



-- 
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...