On Thu, 13.03.14 14:37, Alan Stern (st...@rowland.harvard.edu) wrote:
This question has probably been asked many times before, but I didn't
see it mentioned anywhere on the systemd web site.
I want to create a unit file for a service where the server program
requires an argument or
On Wed, 19.03.14 16:00, Umut Tezduyar (u...@tezduyar.com) wrote:
Hi Alan,
As Cristian has suggested, the correct behavior is letting daemons
pick up the right argument.
Though, there is a hack if you can't re implement the daemon. You
could compute the variables in an ExecStartPre= and
On Wed, 19.03.14 11:36, Alan Stern (st...@rowland.harvard.edu) wrote:
That is, the man page for systemd.exec merely says that files listed in
EnvironmentFile= directives will be read shortly before the process is
executed. It doesn't say whether shortly before means before or
after the
Hi Alan,
As Cristian has suggested, the correct behavior is letting daemons
pick up the right argument.
Though, there is a hack if you can't re implement the daemon. You
could compute the variables in an ExecStartPre= and write them to a
file (/run/yourservice/arg) and point your
On Wed, 19 Mar 2014, Umut Tezduyar wrote:
Hi Alan,
As Cristian has suggested, the correct behavior is letting daemons
pick up the right argument.
Cristian must not have CC'ed me on his reply, because I didn't see it
until I looked at the mailing list archive.
Though, there is a hack if
This question has probably been asked many times before, but I didn't
see it mentioned anywhere on the systemd web site.
I want to create a unit file for a service where the server program
requires an argument or environment value that has to be computed at
run time; it isn't known in advance.
El 13/03/14 15:37, Alan Stern escribió:
sult?
All I have been able to think of is to have ExecStart= run a shell
script that computes the necessary values and then execs the actual
server program. Is there a better way?
That's a workable hack, however the correct solution is to have the
