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?
Also, I do want an interactive boot like the I -- is confirm-spawn the
way to do this?
Thanks in advance for
On Mon, Jul 29, 2013 at 6:11 AM, cov...@ccs.covici.com 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
Canek Peláez Valdés can...@gmail.com wrote:
On Mon, Jul 29, 2013 at 6:11 AM, cov...@ccs.covici.com 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
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,
4 matches
Mail list logo