Bug#815834: mdadm: with systemd as PID 1, no clean way to restart the mdadm monitor

[Francesco Poli]

On Wed, 24 Feb 2016 22:28:37 +0100 Francesco Poli (wintermute) wrote:

[...]
> Wait, there's /lib/systemd/system/mdmonitor.service : is
> 
>   # systemctl restart mdmonitor.service
> 
> or
> 
>   # service mdmonitor restart
> 
> the clean way I am looking for?

I tried to execute

  # service mdmonitor restart

and it seems to correctly restart the mdadm monitor process.

I wonder why there's this mdmonitor.service and mdadm.service is linked
to /dev/null (so that it is masked).
During the mdadm upgrade "invoke-rc.d mdadm stop" and "invoke-rc.d
mdadm start" are executed: they are ineffective, if systemd is PID 1.

Could mdmonitor.service be renamed as mdadm.service?


Please help me understand, in case I am completely off-track.
Thanks for your time!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20160226/335425db/attachment.sig>