Absolute path in systemd file

[Gbury]

As I'm learning, it seems systemd requires an absolute path in the ExecStart command of a service file, which means the current file in data cannot be directly used.

[c-cube]

See option WorkingDirectory -- Simon

[Gbury]

I'm not sure I understand what you mean. For clarification, as far as I understand:

• systemd actually requires that the executable in ExecStart must be an absolute path, which is annoying given that the service file shouldn't need to change when switching compilers with opam
• the working directory is used to determine from where the process will be started, and it appears to be specified as a static path

The only way I see how to use the WorkingDirectory option to solve the problem would be to somehow use opam config var bin, but then again I'm not sure it would help with the absolute path problem.

As a side note, the small commentary about persistent storage using the WorkingDirectory option wasn't very enlightening for me, ^^

[c-cube]

Or use a script in ~/bin that will eval opam config env to find the proper frogutils -- Simon

[c-cube]

Ah. Just use one of the switches? It won't change the behavior of frogutils... -- Simon