On Nov 11, Michael Biebl wrote:
Please boot with systemd.log_level=debug on the kernel command line, the
attach the output of journalctl -alb
I guess these are the relevant lines:
Found ordering cycle on graphical.target/start
Found dependency on multi-user.target/start
Found dependency
Am 12.11.2014 um 14:29 schrieb Uwe Storbeck:
On Nov 11, Michael Biebl wrote:
Please boot with systemd.log_level=debug on the kernel command line, the
attach the output of journalctl -alb
I guess these are the relevant lines:
Found ordering cycle on graphical.target/start
Found
Am 12.11.2014 um 14:44 schrieb Michael Biebl:
Am 12.11.2014 um 14:29 schrieb Uwe Storbeck:
On Nov 11, Michael Biebl wrote:
Please boot with systemd.log_level=debug on the kernel command line, the
attach the output of journalctl -alb
I guess these are the relevant lines:
Found ordering
Am 12.11.2014 um 14:44 schrieb Michael Biebl:
Am 12.11.2014 um 14:29 schrieb Uwe Storbeck:
On Nov 11, Michael Biebl wrote:
Please boot with systemd.log_level=debug on the kernel command line, the
attach the output of journalctl -alb
I guess these are the relevant lines:
Found ordering
On Wed, Nov 12, 2014 at 02:44:53PM +0100, Michael Biebl wrote:
Yeah, it shows that watchdog.service is involved in dependency cycle and
systemd therefore removes it from the transaction.
Why doesn't it show the same reaction on my system then? Uwe's system doesn't
seem to have any changes out
To be sure: what are you trying to do here and why? Maybe we can find a
better solution
Watchdog should be started as late as possible during the boot process and
stopped as early as possible during shutdown.
Btw, is echo /sbin/modprobe $watchdog_module really intended? that
will just
On Wed, Nov 12, 2014 at 03:17:22PM +0100, Michael Biebl wrote:
That's the part that causes the dep cycle afaics.
By being hooked into multi-user.target, watchdog.service will have an
explicit
Before=multi-user.target
dependency.
multi-user.target on the other hand is an alias of
On Nov 10, Michael Meskes wrote:
Could you run 'ls /lib/systemd/system/graphical.target.wants/' please?
# ls /lib/systemd/system/graphical.target.wants/
systemd-update-utmp-runlevel.service
# cat
/lib/systemd/system/graphical.target.wants/systemd-update-utmp-runlevel.service
# This file is
# ls /lib/systemd/system/graphical.target.wants/
systemd-update-utmp-runlevel.service
Exactly the same on my system, no idea where the difference can be.
I guess we need help from somebody who knows systemd much better. :)
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at
Am 11.11.2014 um 13:50 schrieb Michael Meskes:
# ls /lib/systemd/system/graphical.target.wants/
systemd-update-utmp-runlevel.service
Exactly the same on my system, no idea where the difference can be.
I guess we need help from somebody who knows systemd much better. :)
Please boot with
On Wed, Nov 05, 2014 at 05:22:34PM +0100, Uwe Storbeck wrote:
Package: watchdog
Version: 5.14-1
Severity: important
Dear Maintainer,
since the last upgrade watchdog does not get started at boot time:
Nov 05 16:42:52 grappa systemd[1]: Found ordering cycle on
graphical.target/start
On Nov 10, Michael Meskes wrote:
Could you tell me which other services you have included in graphical.target?
On my system the current setup works flawlessly. Could very well be that I
made
a mistake when setting the After: fields.
It's the standard file from the systemd installation, no
On Mon, Nov 10, 2014 at 01:35:51PM +0100, Uwe Storbeck wrote:
It's the standard file from the systemd installation, no manual
changes. /lib/systemd/system/graphical.target:
Could you run 'ls /lib/systemd/system/graphical.target.wants/' please?
I was expecting 'systemctl list-dependencies' but
Package: watchdog
Version: 5.14-1
Severity: important
Dear Maintainer,
since the last upgrade watchdog does not get started at boot time:
Nov 05 16:42:52 grappa systemd[1]: Found ordering cycle on
graphical.target/start
Nov 05 16:42:52 grappa systemd[1]: Breaking ordering cycle by deleting job
14 matches
Mail list logo
