Projects/bash-tasksched
1
0
Fork 0
Code Releases Wiki Activity

Got rid of the final FIXMEs \o/

Browse source
This commit is contained in:
Darren 'Tadgy' Austin 2020-12-21 22:41:01 +00:00
commit 183a4f83a8
1 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

13
tasksched
View file

@ -530,7 +530,7 @@ display_help() {
This must be given as a single argument, enclosed in single (') or double
(") quotes if it contains spaces, and must be a valid date accepted by
'date --date'. Note: by default UTC is expected, but a specifically given
date/time + TZ will be converted to UTC.
date/time + TZ will be converted to UTC.
-q, --quiet
Normally, when the scheduler spec> indicates the job should be run, the
name of the <job ID> is output to stdout. With this option, ${0##*/}
@ -539,7 +539,7 @@ display_help() {
-s <filename>, --statefile <filename>
Use the given <filename> as the state file for maintaining a record of
the last execution time of the job IDs.
The default statefile is $FIXME.
The default statefile is \$HOME/.config/${0##*/}.state.
Using this option allows non-root users to use the scheduler's job
tracking functionallity. If the file provided does not exist, it will
be created if possible, or an error will be emitted if the <filename>
@ -557,15 +557,16 @@ display_help() {
<scheduler spec>
This is the 'crontab' style specification of the schedule on which the
given <job ID> should be executed. This schedule is compared against the
current (or provided by option --date/-d) date/time.
current (or that provided by option --date/-d) date/time.
The schedule is given as a single argument enclosed in single (') or
double (") quotes, with each component separated by spaces. Be mindful of
shell globbing while using a '*' on the command line.
See documentation for a full rundown of the <scheduler spec> accepted.
<job ID>
FIXME
<job ID> may not contain the character ':'. This is only restriction on
job identifications.
A free form identifier used for state tracking between runs.
This is also output to stdout if the schedule is matched against the
date/time. <job ID> may not contain the character ':'. This is only
restriction on job identifications.
EOF
}