ftpwatch(8) [debian man page]

FTPWATCH(8)						      System Manager's Manual						       FTPWATCH(8)

NAME

       ftpwatch - Notifies you of changes on remote ftp servers

SYNOPSIS

       ftpwatch

DESCRIPTION

       ftpwatch is a program intended to be run as a cron job. Every user who wants to use it should install it into his crontab file. That is add
       something like:

	   47 5    * * 7 /usr/bin/ftpwatch

       The user should then create a .ftpwatchrc file. If one is found the specifed files and directories in that file	will  be  dired,  and  the
       result  is  stored as separate files in a .ftpwatch directory i the home directory.  diff(1) is invoked to find any changes since last run.
       If any are found, the output of diff is mailed to the user.

OPTIONS

       -d<opt> passes the options in <opt> to diff when invoked to generate the change-repport sent to the user.

       -p run ftp in passive mode

CONFIGURATION FILES

       Each user can place a .ftpwatchrc file in there home directories, listing the files or directories they are intrested  in.  The	format	is
       simpel. Each line of the file is of the following type:

	   <Host>:<File>

       Where  <Host> is the hostname of the ftp server and <File> is the file or directory to watch. If you instead want to watch an entire direc-
       tory structure recoursly you can add an R to the config line of the dir whoes subdirs you are intresed in, like this:

	   <Host>:R:<File>

AUTHOR

       Hakan Ardo <hakan@debian.org>

								  7 Januari 1997						       FTPWATCH(8)

cron(8) 						      System Manager's Manual							   cron(8)

NAME

       cron - The system clock daemon

SYNOPSIS

       /usr/sbin/cron

DESCRIPTION

       The cron daemon runs shell commands at specified dates and times.  Commands that are to run according to a regular or periodic schedule are
       found within the crontab files.	Commands that are to run once only are found within the at files.  You submit crontab and at file  entries
       by  using  the  crontab	and  at  commands.  Because the cron process exits only when killed or when the system stops, only one cron daemon
       should exist on the system at any given time.  Normally, you start the cron daemon from within a run command file.

       During process initialization and when cron detects a change, it examines the crontab and at files.  This strategy reduces the overhead	of
       checking  for  new  or  changed files at regularly scheduled intervals.	The cron command creates a log of its activities.  The cron daemon
       must be started from the system startup scripts because it must begin execution without a login user ID set.  The cron daemon  starts  each
       job  with the following process attributes stored with the job by the invoking process: Login user ID Effective and real user IDs Effective
       and real group IDs Supplementary groups

       It also establishes the following attributes from the authentication profile of the account associated with the login user ID of the invok-
       ing process: Audit control and disposition masks Kernel authorizations

DIAGNOSTICS

       The at and batch programs will refuse to accept jobs submitted from processes whose login user ID is different from the real user ID.

FILES

       Specifies the command path.  Main cron directory Directory containing the crontab files.  List of allowed users.  List of denied users His-
       tory information for cron Queue description file for at, batch, and cron

RELATED INFORMATION

       Commands:  at(1), crontab(1), rc0(8), rc2(8), rc3(8)

       Files: queuedefs(4) delim off

																	   cron(8)