Timeline for systemd: lie about process name using sh -c exec idiom
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2016 at 18:18 | comment | added | Lee-Man | In that case (still not sure I agree), you might want to create your own shell script with the same name, e.g. /usr/local/bin/foo. This script could call foo-config and then ultimately /usr/bin/foo? (Again, not tested.) | |
| Jun 13, 2016 at 18:15 | comment | added | mwp |
I agree that this approach would be better; unfortunately, I'm trying to wrap something that works a certain way, and I don't have much control over it. Specifically, foo-config does some critical parsing of the config file to generate command-line arguments. This parsing needs to happen at run time to capture any subsequent changes to the config file. Is there a way to do something like Environment=ARGS=$(/usr/bin/foo-config)?
|
|
| Jun 13, 2016 at 18:05 | history | answered | Lee-Man | CC BY-SA 3.0 |