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/008172.html | 124 ++++++++++++++++++++++++++ 1 file changed, 124 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-September/008172.html (limited to 'zarb-ml/mageia-dev/2011-September/008172.html') diff --git a/zarb-ml/mageia-dev/2011-September/008172.html b/zarb-ml/mageia-dev/2011-September/008172.html new file mode 100644 index 000000000..7a6bcbf81 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/008172.html @@ -0,0 +1,124 @@ + + + + [Mageia-dev] systemd vs dm + + + + + + + + + +

[Mageia-dev] systemd vs dm

+ Dick Gevers + dvgevers at xs4all.nl +
+ Sat Sep 17 12:40:04 CEST 2011 +

+
+ +
On Sat, 17 Sep 2011 11:16:57 +0100, Colin Guthrie wrote about Re:
+[Mageia-dev] systemd vs dm:
+
+>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?
+
+pstree is not quite unequivocal, because it shows systemd at the top of
+every running process, even those surely not started by systemd but e.g. by
+the current user.
+
+But on the other hand systemd has PID 1 so it's reasonable to assume
+everything stems from it.
+
+Although when I do lsof |grep rsys |grep syst it returns nothing, so
+perhaps that means rsyslog was not started by systemd: we'd have to compare
+with a system where systemctl status rsyslog.service gives a better result.
+
+"lsof |grep cgrou" returns only one line:
+
+systemd       1             root    6r      DIR               0,18
+0        193 /sys/fs/cgroup/systemd/system
+
+I hope this gives some clues.
+
+Thanks and BFN
+=Dick Gevers=
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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