The proper way to figure out what failed to start and why is to use systemctl
# list of running services systemctl # status of particular service systemctl status name-of-service Now if your concern is the service loading order, then you're really talking about problems in your unit files, i.e., there's a dependency or sequencing instruction that wasn't included. Unlike sysvinit, you don't need a reboot to determine or solve load order problems. On Tue, Jul 30, 2013 at 2:29 AM, <[email protected]> wrote: > Canek Peláez Valdés <[email protected]> wrote: > >> On Mon, Jul 29, 2013 at 6:11 AM, <[email protected]> wrote: >> > I want to -- at least in initial testing -- have systemd not try to do >> > things in parallell -- one at a time is very nice -- I even have openrc >> > configured that way. Any way to do this? >> >> No if you don't use --confirm-spawn AFAIK; the whole parallel start >> thingy is deeply integrated in systemd's design. And, why would you >> want to start things sequentially? > > Because its much easier to figure out things -- particularly if > something has gone wrong -- and I don't boot that often, so I don't > really care if it takes a bit longer -- its certainly a lot less than > that other OS. > > And thanks for your response. > > > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > [email protected] > -- This email is: [ ] actionable [ ] fyi [ ] social Response needed: [ ] yes [ ] up to you [ ] no Time-sensitive: [ ] immediate [ ] soon [ ] none
