On 06/08/2016 05:22 PM, Wilhelm Schuster wrote:
That's a weird, since mdadm_env.sh only gets installed on SUSE systems. See the following line from the Makefile (line 316):
if [ -f /etc/SuSE-release -o -n "$(SUSE)" ]; then $(INSTALL) -D -m 755 systemd/SUSE-mdadm_env.sh \ $(DESTDIR)$(SYSTEMD_DIR)/../scripts/mdadm_env.sh fi
http://git.neil.brown.name/?p=mdadm.git;a=blob;f=Makefile;h=5fd7f166e7e14f24...
Originating commit: http://git.neil.brown.name/?p=mdadm.git;a=commitdiff;h=61c094715836e76b66d7a...
Also, personally I've never seen /usr/lib/systemd/scripts used on Arch. I don't think that's an official (as in used by systemd upstream) directory (though I'm not sure).
Yes, this is strange. It seems like the PKGBUILD should take into consideration that there will be no mdadm_env.sh installed on Arch and tweak the mdmonitor.service file accordingly with sed or the like to either eliminate the EXEC attempt to run the script, or at least install an empty "stub" mdadm_env.sh that does nothing but eliminates the boot error. I'll leave it up to the masterminds here. If this is an issue that needs a bug filed, let me know, I'm happy to file it. -- David C. Rankin, J.D.,P.E.