https://bugzilla.novell.com/show_bug.cgi?id=780259
https://bugzilla.novell.com/show_bug.cgi?id=780259#c33
--- Comment #33 from Bruno Friedmann 2013-11-17 09:00:27 UTC ---
Okay then we have information misleading comprehension.
Previously in /etc/init.d/atd during the start
startproc $ATD_BIN $ATD_ARGS
You finished with a process which clearly indicate how and what option run.
ps auxw ...
Which is perfectly aligned with information contained in man atd
Now running the systemd service you finish only with
/usr/sbin/atd -f
So yes the optional values are there, visible in the status at.service. But not
on the proc line !
My question was wouldn't be better to use something like
EnvironmentFile=/etc/sysconfig/atd
ExecStart=/usr/sbin/atd -f $OPTS
Like the solution fedora has adopted, okay requiring to rewrite the sysconfig
atd file with a one line but would have the advantage to be simplier
Then anybody looking at the daemon ps would seen that the options are there.
Patching code daemon to make them behaving differently than what is expected is
really really strange.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
