[BACK]Return to Domain_Crontab_Entries.tex CVS log [TXT] [DIR] Up to [LON-CAPA] / loncom / html / adm / help / tex
File:  [LON-CAPA] / loncom / html / adm / help / tex / Domain_Crontab_Entries.tex
Revision 1.4: download - view: text, annotated - select for diffs
Tue Jul 29 18:56:08 2008 UTC (16 years ago) by raeburn
Branches: MAIN
CVS tags: version_2_9_X, version_2_9_99_0, version_2_9_1, version_2_9_0, version_2_8_X, version_2_8_99_1, version_2_8_99_0, version_2_8_2, version_2_8_1, version_2_8_0, version_2_7_X, version_2_7_99_1, version_2_7_99_0, version_2_7_1, version_2_7_0, version_2_6_99_1, version_2_10_0_RC2, version_2_10_0_RC1, bz6209-base, bz6209, bz5969, bz2851, PRINT_INCOMPLETE_base, PRINT_INCOMPLETE, HEAD, GCI_3, GCI_2, GCI_1, BZ5971-printing-apage, BZ5434-fox
- Fix label.

    1: \label{Domain_Crontab_Entries}
    2: When LON-CAPA is installed a file named loncapa is written to /etc/cron.d.
    3: The frequency and timing of execution of scripts included in this
    4: loncapa crontab file can be modified to suit the needs of your domain.
    5: The scripts, which are all run as the user 'www', are as follows: 
    6: 
    7: \begin{itemize}
    8: \item \emph{/home/httpd/perl/loncron} run daily at 5.10 am This updates
    9: the list of servers in the LON-CAPA cluster to which your domain belongs.
   10: All servers in this list should be contactable, and will have the
   11: ability to host user sessions for users in the domain, as well as
   12: being available, if designated as library servers, to return responses
   13: to remote searches for files housed there which have been contributed
   14: to the LON-CAPA content repository. Connections to all servers are
   15: re-evaluated by loncron, in case some machines had become unavailable
   16: within the last 24 hours, and had therefore been flagged as temporarily
   17: offline.
   18: \item \emph{/usr/local/loncapa/bin/CHECKRPMS} runs every other day at 3.10
   19: am. This file automates the process of checking for available updates
   20: to LON-CAPA systems. The distprobe script, installed as a part of
   21: LON-CAPA, is used to determine the Linux distribution installed on
   22: the server, which in turn dictates which utility (yum, up2date, you
   23: or rug) is called to perform the package check.
   24: \item \emph{/home/httpd/perl/searchcat.pl} run every other day at 1.10 am
   25: traverses the LON-CAPA resource directory in a domain and gathers
   26: metadata which are entered into a SQL database. The script will repopulate
   27: and refresh the metadata database used for the searching the resource
   28: catalog. The script also refreshes and repopulates database tables
   29: used to store metadata for publicly accessible portfolio files, and
   30: user information needed for user searches in a LON-CAPA domain. 
   31: \item \emph{/home/httpd/perl/cleanup\_database.pl} run daily at 2.13 am
   32: drops tables from the LON-CAPA MySQL database if their comment is
   33: 'temporary' and they have not been modified in a given time (default
   34: is 2 days).
   35: \item \emph{/home/httpd/perl/cleanup\_file\_caches.pl} run daily at 1.05
   36: am removes temporary files from the LON-CAPA print spool, the multidownload
   37: zip spool, and userfiles cache.
   38: \item \emph{/home/httpd/perl/Autoenroll.pl} run daily at 1.30 am updates
   39: classlists for any LON-CAPA courses for which auto-enrollment is active,
   40: if enabled in the domain. A conduit needs to have been established
   41: to institutional course roster information. 
   42: \item \emph{/home/httpd/perl/Autoupdate.pl} run daily at 3.30 am can reconcile
   43: first name, last name etc. information stored in LON-CAPA with authoritative
   44: data available from an institutional directory. A conduit needs to
   45: have been established to the institutional data source. 
   46: \end{itemize}
   47:
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>