> Sure; just look as "man systemd" how to enable debug output.
How embarrassing for me ;)
Thank you, exactly what I needed to continue.
I narrowed it down to a service, of which I do not need. Problem solved.
Thanks again and apologies for not just checking the man page!
On Mon, Nov 23, 2015
24.11.2015 06:37, Jesse Cobra пишет:
It is not happening at this moment but last week I saw these messages in
dmesg:
[ 755.629529] systemd[1]: Cannot add dependency job for unit
dmesg.service, ignoring: Unit dmesg.service is masked.
[ 5177.325999] systemd[1]: Cannot add dependency job for unit
It is not happening at this moment but last week I saw these messages in
dmesg:
[ 755.629529] systemd[1]: Cannot add dependency job for unit
dmesg.service, ignoring: Unit dmesg.service is masked.
[ 5177.325999] systemd[1]: Cannot add dependency job for unit
dmesg.service, ignoring: Unit dmesg.se
Am 24.11.2015 um 01:49 schrieb Jesse Cobra:
I wish I had more info.
jesus christ you talk about "I often seesystemd events logged in dmesg"
without posting them
Does systemd itself have a log file?
Not the service I am creating but systemd itself.
--
Messa
I wish I had more info.
Does systemd itself have a log file?
Not the service I am creating but systemd itself.
--
Message: 5
Date: Sat, 21 Nov 2015 11:58:51 +0100
From: Reindl Harald
To: [email protected]
Subject: Re: [systemd-devel] general
Am 21.11.2015 um 09:00 schrieb Jesse Cobra:
I often see systemd events logged in dmesg at this same time also at
1500 seconds or intervals of 1500 seconds. It could be totally unrelated.
Anyways, does SystemD itself have a log or a config file or some timeout
setting around this?
a good star
Sorry if this is the wrong place to ask this!
I am trying to investigate an issue on one of my linux systems. It is a
pretty normal yocto install, kernel 3.10.17 and is running an ALSA loopback
type audio application.
Every 25 minutes (1500 seconds) or some interval of that I see an underrun
with
