From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-September/008171.html | 163 ++++++++++++++++++++++++++ 1 file changed, 163 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-September/008171.html (limited to 'zarb-ml/mageia-dev/2011-September/008171.html') diff --git a/zarb-ml/mageia-dev/2011-September/008171.html b/zarb-ml/mageia-dev/2011-September/008171.html new file mode 100644 index 000000000..25401fd30 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/008171.html @@ -0,0 +1,163 @@ + + + + [Mageia-dev] systemd vs dm + + + + + + + + + +

[Mageia-dev] systemd vs dm

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Sat Sep 17 12:16:57 CEST 2011 +

+
+ +
'Twas brillig, and Dick Gevers at 17/09/11 10:36 did gyre and gimble:
+> On Sat, 17 Sep 2011 10:02:03 +0100, Colin Guthrie wrote about Re:
+> [Mageia-dev] systemd vs dm:
+> 
+>> So does:
+>>
+>> systemctl restart rsyslog.service
+>>
+>> work?
+> 
+> Not really:
+> 
+> # systemctl restart rsyslog.service
+> # systemctl status rsyslog.service
+> rsyslog.service - System Logging Service
+>           Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled)
+>           Active: failed since Sat, 17 Sep 2011 09:30:29 +0000; 8s ago
+>          Process: 23407 ExecStart=/sbin/rsyslogd -n -c5 (code=exited,
+> status=1/FAILURE) Process: 23404 ExecStartPre=/bin/systemctl stop
+> systemd-kmsg-syslogd.service (code=exited, status=0/SUCCESS) CGroup:
+> name=systemd:/system/rsyslog.service
+> #
+> 
+>> And finally, can you run: /sbin/rsyslogd -n -c5 manually or does it exit
+>> out with return code 1 also?
+> 
+> # /sbin/rsyslogd -n -c5
+> Pidfile (and pid) already exist.
+> 
+> and:
+> # ps -eLF |grep rsys
+> root      1104     1  1104  0    4 60184  1512   0 Sep16 ?        00:00:00
+> rsyslogd -c 4
+> root      1104     1  1130  0    4 60184  1512   4 Sep16 ?        00:00:00
+> rsyslogd -c 4
+> root      1104     1  1131  0    4 60184  1512   0 Sep16 ?        00:00:00
+> rsyslogd -c 4 
+> root      1104     1 1132  0    4 60184  1512   2 Sep16 ?        00:00:00
+> rsyslogd -c 4 
+> ...
+> 
+> And lsof shows that all relevant logs are touched by the rsyslog daemon. So
+> my guess is that only the systemd status message is bad, but the service is
+> running correctly.
+
+Well that's slightly disturbing. It seems that rsyslog was started but
+not by systemd.
+
+Can do do some kind of pstree type analysis (perhaps also using cgroups
+stuff) to work out what process actually started rsyslog?
+
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1