21 Dec
2019
21 Dec
'19
5:13 p.m.
The startjob that hangs is "Hold".
A start job is running for Hold unt… finishes up (7min 23s / no limit)
I have tried setting the timout to a low number to address this issue,
but it does not seem to fix this problem. Perhaps I did not set it in
the right way/place.
On 12/21/19 2:37 AM, Thierry de Coulon wrote:
On Saturday 21 December 2019 00.52:35 James D Freels
wrote:
(...)
If I boot up under TDM (after running
dpkg-reconfigure tdm-trinity first
to initiate TDM into the boot sequence), it starts fine, but
continuously hangs in the main console with one of the infamous systemd
problems wherein we get the "a startjob is running ..." and it NEVER
ends until rebooted.
(...)
Essentially, I
have NO virtual consoles at all.
(...)
It is at this point, where I need some help in
how to fix it, and I
suspect that all debian/buster users may have the same issue, but not
sure of course.
Hello,
I am running Buster with the preliminary builds too and I am not having this
issue. I have set the timout to 5s however.
What is the startjob that hangs?
Thierry
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting