Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
The ONE Campaign to make poverty history

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 125 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

cron



SYNOPSIS

       cron


DESCRIPTION

       Cron  should be started from /sbin/init.d/cron, /etc/rc or
       /etc/rc.local.  It will return immediately, so  you  don't
       need to start it with '&'.

       Cron searches /var/spool/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)).    Additionally,  cron  reads  the  files  in
       /etc/cron.d; it treats the files in /etc/cron.d as  exten­
       sions  to  the  /etc/crontab file (they follow the special
       format of that file, i.e. they include  the  user  field).
       The  intended purpose of this feature is to allow packages
       that require finer control of their  scheduling  than  the
       /etc/cron.{daily,weekly,monthly}  directories allow to add
       a crontab file to /etc/cron.d. Such files should be  named
       after  the  package that supplies them. Files must conform
       to the same naming convention  as  used  by  run-parts(8):
       they must consist solely of upper- and lower-case letters,
       digits, underscores, and hyphens. Like  /etc/crontab,  the
       files  in  the  /etc/cron.d  directory  are  monitored for
       changes.  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).

       Additionally,  cron checks each minute to see if its spool
       directory's modtime (or the modtime on  /etc/crontab)  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 whenever a crontab file is mod­
       ified.  Note that the crontab(1) command updates the  mod­
       time of the spool directory whenever it changes a crontab.


SEE ALSO

       crontab(1), crontab(5)


AUTHOR

       Paul Vixie <paul@vix.com>

                         20 December 1993                 CRON(8)
  
Help us cut cost by not downloading the whole site!
Use of automated download sofware ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and therefore is expressedly prohibited. For more details on this, take a look here

Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds