kep_reload(1) [debian man page]

KEP_RELOAD(1)						      General Commands Manual						     KEP_RELOAD(1)

NAME

       kep_reload - Update Predict's Keplerian elements

SYNOPSIS

	kep_reload

DESCRIPTION

       KEP_RELOAD is a simple utility that forces an immediate reload of PREDICT's Keplerian database through a socket connection while PREDICT is
       running in server mode.	It is especially useful in environments where PREDICT runs continuously, and periodic  Keplerian  element  updates
       are made outside of PREDICT, such as through scripts run through a crontab.

       The  "kepupdate"  script  found	in this directory is an example of a Keplerian element update script that can be run on an automated basis
       through a crontab.  It is designed to be placed in your home directory under a subdirectory  called  "cronjobs".   It  downloads  Keplerian
       orbital	data  from  www.celestrak.com  using  the  HTTP  protocol.   (The  "wget" utility, available from the Free Software Foundation, is
       required, and is included in many Linux distrubutions.)

       Type crontab -e to edit your crontab.  Simply add the following entry:

	       0 8 * * * kepupdate

       and your orbital database will update each morning at 8:00 AM (provided you have a network connection at that time).

       See the crontab man page for more information on editing your crontab.

AUTHOR

       This man page was written by A. Maitland Bottoms, AA4HS, for Debian GNU/Linux.

								  31 August 2003						     KEP_RELOAD(1)

CRONTAB(1)						      General Commands Manual							CRONTAB(1)

NAME

       crontab - maintain crontab files for individual users (ISC Cron V4.1)

SYNOPSIS

       crontab [-u user] file
       crontab [-u user] [-l | -r | -e]

DESCRIPTION

       Crontab	is  the  program  used	to install, deinstall or list the tables used to drive the cron(8) daemon in ISC Cron.	Each user can have
       their own crontab, and though these are files in /var, they are not intended to be edited directly.

       If the cron.allow file exists, then you must be listed therein in order to be allowed to use this command.  If the cron.allow file does not
       exist  but  the	cron.deny  file does exist, then you must not be listed in the cron.deny file in order to use this command.  If neither of
       these files exists, only the super user will be allowed to use this command.

       If the -u option is given, it specifies the name of the user whose crontab is to be tweaked.  If this option is not given, crontab examines
       "your"  crontab,  i.e.,	the  crontab of the person executing the command.  Note that su(8) can confuse crontab and that if you are running
       inside of su(8) you should always use the -u option for safety's sake.

       The first form of this command is used to install a new crontab from some named file or standard input  if  the	pseudo-filename  ``-''	is
       given.

       The -l option causes the current crontab to be displayed on standard output.

       The -r option causes the current crontab to be removed.

       The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables.  After you exit
       from the editor, the modified crontab will be installed automatically.

SEE ALSO

       crontab(5), cron(8)

FILES

       /etc/cron.allow
       /etc/cron.deny

STANDARDS

       The crontab command conforms to IEEE Std1003.2-1992 (``POSIX'').  This new command syntax differs from previous versions of Vixie Cron,	as
       well as from the classic SVR3 syntax.

DIAGNOSTICS

       A fairly informative usage message appears if you run it with a bad command line.

AUTHOR

       Paul Vixie <vixie@isc.org>

4th Berkeley Distribution					 29 December 1993							CRONTAB(1)