>From 95df61cb2b258b972faeb472dd6a84765a2e6b1d Mon Sep 17 00:00:00 2001 From: Antono Vasiljev Date: Fri, 20 Jan 2012 13:07:46 +0300 Subject: [PATCH 2/2] Updated texinfo manual with $XDG_CONFIG_HOME --- mcron.texinfo.in | 37 ++++++++++++++++++------------------- 1 files changed, 18 insertions(+), 19 deletions(-) diff --git a/mcron.texinfo.in b/mcron.texinfo.in index 9fe1d05..81c7a73 100644 --- a/mcron.texinfo.in +++ b/mcron.texinfo.in @@ -193,7 +193,7 @@ how to run mcron to make them happen. @cindex example, run a program every hour You have an executable @code{my-program} in your home directory, which you want to run every hour. Create a file @code{job.guile} in directory address@hidden/.cron} with the following contents address@hidden/.config/cron} with the following contents @example (job '(next-hour) "my-program") @@ -224,7 +224,7 @@ also the next section) and run the @code{mcron} command. If you want to run other jobs, you can either add more lines to this -file, or you can create other files in your @code{.cron} directory +file, or you can create other files in your @code{~/.config/cron} directory with the @code{.guile} extension. Alternatively, you can use any file you want and pass it as an argument to @code{mcron}, or even pipe the commands into the standard input. @@ -237,7 +237,7 @@ commands into the standard input. @cindex vixie examples You have an executable @code{my-program} in your home directory, which you want to run every hour. Create a file @code{job.vixie} in directory address@hidden/.cron} with the following contents address@hidden/.config/cron} with the following contents @example 0 * * * * my-program @@ -808,20 +808,19 @@ place in the part which implements the mcron personality. @cindex mcron arguments @cindex command line, mcron @cindex mcron command line -Mcron should be run by the user who wants to schedule his jobs. It may -be made a background job using the facilities of the shell. The basic -command is address@hidden [OPTION ...] [file ...]} -which has the effect of reading all the configuration files specified -(subject to the options) and then waiting until it is time to execute -some command. If no files are given on the command line, then mcron -will look in the user's ~/.cron directory. In either case, files which -end in the extension .vixie or .vix will be assumed to contain -Vixie-style crontabs, and files ending .guile or .gle will be assumed -to contain scheme code and will be executed as such; ANY OTHER FILES -WILL BE IGNORED - specify a file name of ``-'' and then pipe the files -into the standard input if you really want to read them, possibly -using the @code{stdin} option to specify the type of file. +Mcron should be run by the user who wants to schedule his jobs. It +may be made a background job using the facilities of the shell. The +basic command is @code{mcron [OPTION ...] [file ...]} which has the +effect of reading all the configuration files specified (subject to +the options) and then waiting until it is time to execute some +command. If no files are given on the command line, then mcron will +look in the user's @code{~/.config/cron} directory. In either case, +files which end in the extension .vixie or .vix will be assumed to +contain Vixie-style crontabs, and files ending .guile or .gle will be +assumed to contain scheme code and will be executed as such; ANY OTHER +FILES WILL BE IGNORED - specify a file name of ``-'' and then pipe the +files into the standard input if you really want to read them, +possibly using the @code{stdin} option to specify the type of file. The program accepts the following options. @@ -1109,8 +1108,8 @@ The last component of the name of the program was not one of @code{mcron}, @code{cron}, @code{crond} or @code{crontab}. @item 13 -Either the ~/.cron directory does not exist, or there is a problem -reading the files there. +Either the ~/.config/cron directory does not exist, or there is a +problem reading the files there. @c @item 14 @c There is a problem writing to /var/cron/update. This is probably -- 1.7.5.4