4 # cron default bits to add at top of crontab...
5 # by fred t. hamster, GNU GPL v3 license.
7 # these stanzas are assumed to be present in every one of the other cron
8 # example files. unfortunately there is no way to include cron files in other
9 # cron files, so the functional parts here should just be pasted directly into
12 # set the shell to bash. (not the default for some cron implementations.)
15 # crontab miniature docs:
17 # below is the short form key to the crontab positional entries for times:
18 # m h dom mon dow command
20 # below is a longer form that spells out the meaning of each position:
21 # minute(s) hour(s) dayOfMonth(s) month(s) dayOfWeek(s) command
23 # each field is optionally plural because cron allows each of the positions to
24 # indicate multiple values. generally it is simpler and sufficient to have a
25 # single value in the field, but there are also good reasons that some tasks
26 # would have a more complicated formula (such as, "every couple of days" rather
29 # the wildcard '*' indicates that every valid value is okay for that field.
30 # the wildcard form of a crontab line is this: "* * * * * command"
31 # that "command" will execute every single minute.
33 # set a user name for writing unique log files. this is important because
34 # cron doesn't have the variable USER defined. cron does define HOME, which
35 # is pretty lucky for us...
36 # you may want to use a more appropriate user name than mine, which is "fred".
39 # the guts of the crontab would follow below. this usually is a set of valid
40 # crontab lines that spell the time or times for commands to be executed. my
41 # crontabs usually have from 3 to 8 entries because i tend to atomicize the
42 # tasks, rather than writing big complicated multi-purpose scripts. not saying
43 # that's always better, it's just how i roll (my crontabs)...
45 # also, it is fine to have a really long command with multiple sub-commands;
46 # just put it inside parentheses to group a bunch of commands together. there
47 # are many examples of doing this in the other crontab examples in this folder.
49 # further, it's often important to send the output from the cron job to an
50 # output location. doing this keeps cron from sending you a lot of emails
51 # with cron job output on some systems. you can use the normal output
52 # redirection operators to do this (e.g. '>', '2>', '&>', '>>' and '&>>').
53 # /dev/null works as an output target if you don't ever want to see the
54 # results from your cron jobs. i usually prefer to write log files in the /tmp
55 # directory with the ${USER} variable in the file name. here's an example of
56 # a real command with output that will *append* both output and error streams
57 # ('&>>') to an output file. if your output can be huge, then you may want to
58 # overwrite the output file instead ('&>').
60 # runs every minute and recreates a fortune for thunderbird signature.
61 # a lot of the detail below is to get the feisty meow environment loaded for
63 * * * * * (export LIGHTWEIGHT_INIT=true; source $HOME/feisty_meow/scripts/core/launch_feisty_meow.sh; perl $HOME/feisty_meow/scripts/text/new_sig.pl) &>>/tmp/${USER}-cron-nechung_fortune.log