canto-fetch(1) [debian man page]
Canto-fetch(1) Canto-fetch Canto-fetch(1) NAME
Canto-fetch - A quiet feed fetcher. DESCRIPTION
Canto-fetch is designed to be run through a cron job, every minute. Every time it's run, it checks the timestamp on each index file and updates the feed, if necessary. The format it produces is a simple UTF-8 encoded, NULL delimited text file on disk, readable by the canto client. GETTING STARTED
Canto-fetch is meant to be used through a cron, adding this line to your crontab will cause canto-fetch to poll every minute. * * * * * canto-fetch Alternatively, if you're unable/uncomfortable using cron, canto-fetch has a background daemon mode so you can invoke it in your X session scripts. Just use canto-fetch -b USAGE
These options correspond to options to the canto client. -h / --help Print usage and quit. -v / --version Print version and quit. -V / --verbose Output status while updating. -d / --daemon Continue to check for updates every minute. Mostly for debugging with -V, users probably want -b to background. -b / --background Detach from the terminal (implies -d) -f / --force Force updates on all feeds, ignoring timestamps. -s / --sysfp Use feedparser on system instead of builtin copy. -C / --conf [PATH] Set path to configuration file (default: ~/.canto/conf) -F / --fdir [PATH] Set path to feed directory (default: ~/.canto/feeds/) -L / --log [PATH] Set path to log (default: ~/.canto/fetchlog) -S / --sdir [PATH] Set the path to execurl scripts (default ~/.canto/scripts/) FILES
~/.canto/fetchlog Canto-fetch log file. ~/.canto/feeds/ This is the directory where canto-fetch records stories. BUGS
None known, but it's not outside of the realm of possibility =P. HOMEPAGE
http://codezen.org/canto AUTHOR
Jack Miller <jack@codezen.org> Version 0.7.10 27 July 2010 Canto-fetch(1)
Check Out this Related Man Page
CRON(8) BSD System Manager's Manual CRON(8) NAME
cron -- daemon to execute scheduled commands (ISC Cron V4.1) SYNOPSIS
cron [-n] [-x debugflags] DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5). It will return immediately so you don't have to start it with '&'. cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists, and executes each file as a crontab. When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that: - Start with a '.' or a '#'. - End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''. - Are of zero length. - Their length is greater than MAXNAMLEN. cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if such exists). Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num- ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates these log files with compression to preserve disk space. Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed, and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted when- ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab. The following options are available: -x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on, cron writes some additional debugging information to system log during its work. Available debugging flags are: sch scheduling proc process control pars parsing load database loading misc miscellaneous test test mode - do not actually execute any commands bit show how various bits are set (long) ext print extended debugging information -n Stay in the foreground and don't daemonize cron. Daylight Saving Time and other time changes Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre- quently are scheduled normally. If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time has moved backward, care is taken to avoid running jobs twice. Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately. SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files. Natu- rally this is not relevant if cron was built to use syslog(3). FILES
/var/cron/tabs cron spool directory /etc/crontab system crontab file /etc/cron.d/ system crontab directory /var/log/cron log file for cron events SEE ALSO
crontab(1), crontab(5) AUTHORS
Paul Vixie <vixie@isc.org> BSD
October 12, 2011 BSD