21 Dec
2019
21 Dec
'19
5:51 p.m.
On Saturday 21 December 2019 09:18:53 Nikolaus Klepp wrote:
Anno domini 2019 Sat, 21 Dec 12:14:33 -0500
James D Freels scripsit:
Most who have had problems with the system hanging would seem to blame it on
systemd, and have switched from Debian to Devuan. If your hardware is old,
and your resources limited, this might be a good choice. I have had no system
hangups whatsoever since making the move to Devuan.
However, it may not be everybody's way; and what really matters, for the
actual user, is what works, because we have other things to do besides
wrestling with our machines to get them to behave.
Michele Calgaro gave a solution that works for her; look under these headings:
"Re: [trinity-users] Has systemd broken Debian this time?" (15 July 2019)
"Re: [trinity-users] Systemd" (27 July 2019).
I quote her solution from the latter email:
****
You can uncomment the line with DefaultTimeoutStartSec and
DefaultTimeoutStopSec in /etc/systemd/system.conf
DefaultTimeoutStartSec=5s
DefaultTimeoutStopSec=5s
Works like a charm.
Cheers
Michele
****
I hope this may be of some help. This assumes, of course, that the problem may
be with systemd, and not with tdm.
Bill
I could certainly try this if you give me the
specifics of how you did
it. Thanks for the feedback
#apt-get install haveged
... might be sufficient. The rest of my post contains info on how to get it
done on sysv - don't know how to do it on systemd.
Nik
> On 12/21/19 3:00 AM, Dr. Nikolaus Klepp wrote:
> > Anno domini 2019 Sat, 21 Dec 08:37:32 +0100
> >
> > Thierry de Coulon scripsit:
> >> 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?
> >
> > May not be of much use (Devuan here) but RND takes an eternity to
> > create entropy and blocks anthing with network written on it (ssh,
> > ...). "haveged" lightens the burden a bit (takes ~ 1 minute to
start),
> > but I had to modify the sysv scripts to send all offending processes to
> > the background. Now I'm back to 15 sec. boottime.
> >
> >> Thierry
> >>