The standard way to customize any systemd units on ubuntu is to use
drop-ins, or full replacements of units.
For example use: `systemctl edit foo.service' or `systemctl edit --full
foo.service'.
Including environmental files was only available as part of migration
from sysv-init / upstart, and is not the right way to override and
customize units by the administrator going forward.
By default logs go to journal, and are forwarded to syslog as well. What
does --syslog give you, which doesn't get logged into syslog already?
--test is not appropriate for the default cofiguration, nor this unit by
default, as such exit statuses would be treated as failures by systemd.
If one wishes to use --test disabling this unit, and making a custom one
is the way forward. As the meaning of --test is quite different.
** No longer affects: mdadm
** Changed in: mdadm (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642402
Title:
[ubuntu 16.10] mdmonitor.service does not use syslog or environment
file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1642402/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
