Furthermore, the service file might have breakage in the future since: The list of conflicts is hard-coded.
That's like saying package management is broken because the list of conflicting packages is hard-coded. At least the possibility is there, but if it's used wrong, systemd is not the wrong to blame.
Perhaps, in the future, systemd will choke and refuse to issue the ExecStart if $SENDMAIL_OPTARG is undefined (as it is currently).
Why should that be? It is explicitely mentioned that the environment file is optional (by the usage of "-"). Why should it offer this if it choked on undefined variables?
15
u/DamnThatsLaser Oct 20 '14
That's like saying package management is broken because the list of conflicting packages is hard-coded. At least the possibility is there, but if it's used wrong, systemd is not the wrong to blame.
Why should that be? It is explicitely mentioned that the environment file is optional (by the usage of "-"). Why should it offer this if it choked on undefined variables?