[arch-general] mdmonitor.service failed to start
Sander Jansen
s.jansen at gmail.com
Tue Jun 24 12:33:57 EDT 2014
Just opened a bug report since we probably should get rid of mdadm.service.
https://bugs.archlinux.org/task/40965
On Tue, Jun 24, 2014 at 11:25 AM, Sander Jansen <s.jansen at gmail.com> wrote:
>
>
> On Tue, Jun 24, 2014 at 10:56 AM, Paul Gideon Dann <pdgiddie at gmail.com>
> wrote:
>
>> On Tuesday 24 Jun 2014 10:07:31 Sander Jansen wrote:
>> > > But the new problem is: Why this service automatically start? I never
>> > > manually enabled mdmonitor, and I cannot find its link in
>> > > /etc/systemd/system/ .
>> > >
>> > > Regards.
>> >
>> > It's part of the udev rule in
>> /usr/lib/udev/rules.d/63-md-raid-arrays.rules
>>
>> I was a little puzzled by this too, but what confused me most is why
>> there are two unit files
>> provided by mdadm: mdmonitor.service and mdadm.service. I had the latter
>> enabled
>> previously, but the former is started automatically now. I had to disable
>> mdadm.service,
>> because it now clashes with the automatically-started mdmonitor. No
>> problem, but it did
>> strike me as a little odd.
>>
>> I like that md monitoring happens automatically now, though. That's a
>> good idea.
>>
>
> It looks like the mdadm.service seems to be a arch-package specific file.
> Probably before mdadm contained any systemd specific files itself.
>
> Sander
>
More information about the arch-general
mailing list