Re: Buster without systemd?
David Wright wrote:
> On Mon 23 Mar 2020 at 20:27:31 (+0100), Klaus Singvogel wrote:
> > My reasons:
[…]
>
> > My computer "hickups" for 20 seconds at boot. With systemd I don't have
> > the slighest idea which process delays, as several processes start after
> > the delay at once. I had the feeling with Init scripts it was more obvious
> > to see which "startup file" hangs.
>
> $ systemd-analyze critical-chain
>
> Is that any help in finding what's waiting for what?
graphical.target @23.269s
└─multi-user.target @23.269s
└─exim4.service @23.095s +174ms
└─network-online.target @23.092s
└─network.target @23.086s
└─networking.service @1.383s +21.702s
└─ifupdown-pre.service @285ms +1.096s
└─systemd-udev-trigger.service @230ms +54ms
└─systemd-udevd-control.socket @228ms
└─system.slice @218ms
└─-.slice @218ms
At least I found a hint where to start: networking.service
> > But some important messages are not found in syslog nor messages.
>
> Which ones are missing?
When daemons are started (at boot) and how long the startup took for example.
> > No easy way to find out: if and what fails. Example: After months I found
> > out that mlocate doesn't update it's database anymore: previously updates
> > were done by cron, but the distri moved to systemd's way (timer) and by
> > default the updatedb was disabled.
>
> I've not touched the default. What did you have to change to make it run?
Well, this time it was only systemd related, but not Debian. I'm also
running SUSE Linux, and it happened there.
Regards,
Klaus.
--
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D 1994-06-27
Reply to: