RFE: allow variable expansion in command in ExecStart
Open
Nobody has claimed this yet.
pid1
RFE 🎁
- Dominant language
- C
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 140
Description
Guided by the (broken) example:
https://celery.readthedocs.org/en/latest/tutorials/daemonizing.html#usage-systemd
I got this:
[/etc/systemd/system/celery.service:22] Executable path is not absolute, ignoring: $CELERY_BIN multi stopwait $CELERYD_NODES --pidfile=$CELERYD_PID_FILE
Nothing clued me in (at least for a while) that using a variable as the first argument wasn't acceptable. Could you test for that and provide a more informative message? Think of the man-(/woman-)hours saved! :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating systemd's ExecStart parsing and absolute-path validation, then trace how the documented Celery example reaches the diagnostic. Done means variable-based first arguments are handled as requested or rejected with a more informative message, with coverage for the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100