CRON on Unix Server

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Find and delete files and folders which are n days older from one unix server to another unix server

Hi All, Let me know how can i find and delete files from one unix server to another unix server which are 'N' days older. Please note that I need to delete files on remote unix server.So, probably i will need to use sftp, but question is how can i identify files and folders which are 'N'...

2. UNIX for Dummies Questions & Answers

Keep Server Alive with Cron Job

Despite my best efforts, my media streaming server still dies sometimes and I am in a random place trying to ssh into the server to restart it on my cell phone after customers start calling.... I tried using google to track down a script that would do the following Every 5 min execute: sudo...

3. Shell Programming and Scripting

Connecting to multiple unix server from unix server using shell script

Hi Gurus, I'm a unix newbie and I would like to connect to multiple unix servers from unix server using shell script i.e from server a to server b,c,d etc. I want to copy the files from unix server a to server b, c, d. I can access staright using ssh without the need to have password and user...

4. UNIX for Dummies Questions & Answers

To copy a file from one unix server to another unix server through scripts

I am getting the fallowing error when i am trying to execute the scp commomd in shell script warning: You have no controlling tty. Cannot read confirmation. warning: Authentication failed. Disconnected; key exchange or algorithm negotiation failed (Key exchange failed.). scp2: warning: ssh2...

5. UNIX for Advanced & Expert Users

Cron jobs in a unix server

Dear all, Is it possible to view all the cronjobs set under all the userids in a server. Or view all the cronjobs in the server? Thanks in anticipation, Sree.

6. Shell Programming and Scripting

How to connect unix server to unix server through shell scripts

Hi, I would like to connect UNIX server to UNIX server through shell scripts and i have some concepts . But i am totally confused how to connect UNIX server to UNIX server throuth running a script. It will be greatful to me if any buddy will help me. with simple example please. Thanks in...

7. Shell Programming and Scripting

How to connect unix server to unix server through shell scripts

8. UNIX for Dummies Questions & Answers

Server moved, new IP, broken CRON job

Due to downsizing and attrition, I have inherited SysAdmin tasks, but unfortunately not all the required knowledge and skills came to me along with the assignment -> so I appreciate any advice and help ( be patient with my newbie terms and questions). We moved a central server and changed it's...

9. UNIX for Dummies Questions & Answers

CRON Job - saving to a different server?

Thanks for the all the help last evening on CRON jobs. It's now working. Is it possible with cron to save a backup of a file to a different server or location? The idea being that if one host goes arse over tit, I'll have a backup of the DB on another server? Many thanks, Ed Ludlow

LEARN ABOUT SUSE

cron

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

NAME

       cron - daemon to execute scheduled commands (ISC Cron V4.1)

SYNOPSIS

       cron [-l load_avg] [-n]

DESCRIPTION

       Cron  should  be started from /etc/rc or /etc/rc.local.	It will return immediately, so you don't need to start it with '&'.  The -n option
       changes this default behavior causing it to run in the foreground.  This can be useful when starting it out of init.

       Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory.  Cron
       also  searches  for  /etc/crontab  and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)).  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 execut-
       ing  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 modified.  Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.

   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.

   PAM Access Control
       On  SUSE  LINUX	systems,  crond  now  supports	access	control with PAM - see pam(8).	A PAM configuration file for crond is installed in
       /etc/pam.d/crond .  crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.

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.
       Naturally this is not relevant if cron was built to use syslog(3).

CAVEATS

       In this version of cron, /etc/crontab must not be writable by any user other than root.	No crontab files may be links, or linked to by any
       other file.  No crontab files may be executable, or be writable by any user other than their owner.

SEE ALSO

       crontab(1), crontab(5), pam(8)

AUTHOR

       Paul Vixie <vixie@isc.org>

4th Berkeley Distribution					 10 January 1996"							   CRON(8)

UNIX for Advanced & Expert Users