Jan Engelhardt wrote:
On Thursday 2013-11-07 09:12, Per Jessen wrote:
I've just upgraded a box running 13.1M4 to
RC2 - before I did so, I
noticed that mdadm was running, for some strange reason. So I stopped
and disabled it. After upgrading (zypper up), mdadm was back up and
# systemctl status mdadm.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
Well, there is no service. Whatever you see must have been "manually"
started (shell script, or whatever else).
But what exactly is it that is running? Is it perhaps mdadmd
rather than mdadm?
Yup, you're right:
# systemctl status mdadmd
mdadmd.service - LSB: mdadmd daemon monitoring MD devices
Loaded: loaded (/etc/init.d/mdadmd)
Active: inactive (dead) since Thu 2013-11-07 09:18:25 CET; 1h 57min
Process: 2382 ExecStop=/etc/init.d/mdadmd stop (code=exited,
Process: 2142 ExecStart=/etc/init.d/mdadmd start (code=exited,
Nov 07 09:04:01 chestnut systemd: Starting LSB: mdadmd daemon
monitoring MD devices...
Nov 07 09:04:02 chestnut mdadmd: Starting mdadmd ..done
Nov 07 09:04:02 chestnut systemd: Started LSB: mdadmd daemon
monitoring MD devices.
Nov 07 09:18:25 chestnut mdadmd: Shutting down mdadmd ..done
In the above, I had renamed the binary, so the LSB script wouldn't find
it. I'm guessing that I left out a 'd' when I disabled too.
Interstingly, systemctl doesn't complain:
# systemctl disable mdadm.sercvice
# systemctl disable mdadm.sercvice99
Doesn't seem to mind. (surely an error message would not go amiss
# systemctl disable mdadmd
mdadmd.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig mdadmd off
I'm not sure why mdadmd was installed by default, but maybe it's not
such a bad choice.
Per Jessen, Zürich (15.2°C)
- dedicated server rental in Switzerland.
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org