Correct system cron scope guidance
This commit is contained in:
1 file changed
+3
-2
+3
-2
@@ -252,8 +252,9 @@ Notes:
|
|||||||
- Cron accepts a single schedule.
|
- Cron accepts a single schedule.
|
||||||
- Cron environment variables are not supported yet; passing `--env` with
|
- Cron environment variables are not supported yet; passing `--env` with
|
||||||
`--cron` is rejected rather than silently ignored.
|
`--cron` is rejected rather than silently ignored.
|
||||||
- Cron jobs are always created for the current user. `--system` selects system
|
- Cron jobs are created for the current user by default. With `--system` (root
|
||||||
scope for systemd timers and is rejected for cron.
|
only), schedls creates a system cron drop-in; use `--run-as USER` to choose
|
||||||
|
the account that runs it.
|
||||||
- `new --timer` defaults to user scope. System scope requires appropriate
|
- `new --timer` defaults to user scope. System scope requires appropriate
|
||||||
privileges; `schedls` never runs `sudo` for you.
|
privileges; `schedls` never runs `sudo` for you.
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user