Crontab do not run on PM hours Post: 302622679

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

crontab every 2 minutes, 24 hours and once a week

can someone please check my answers for the crontabs I am making 1. how would I set up a crontab tab executes every 2 minutes each and every day of the week? answer: 2 * * * * /path/to/file.pl <-- is this correct? 2. how would I set up a crontab that executes every 24 hours at 2am?...

2. Shell Programming and Scripting

How to make a script run for a maximum of "x" number of hours only

3. Solaris

How to define every 5 hours in Crontab

Hi Experts, I want to run a script which will move the files from particular directory to another backup directory After EVERY 5 hour. How can I put it in crontab- 5 hours!!! * * * * /home/movefilescritp.sh //purple

4. Solaris

crontab to run every 20 second

Hi experts, I want to set the crontab for my script which will run every 20 seconds I think below could be the possible one- */3 * * * * /export/home/username/scripts/runing.sh As my system(SOLARIS 9) is live- i am confused to implement before make sure !!! I need...

5. UNIX for Dummies Questions & Answers

Execute crontab for every 4 hours and begin from current time

I want to add a crontab entry which should execute for every 4 hours and that 4 hours calculation should begin from the current time. Normally if I set the crontab entry like this, 00 */4 30 05 * root date >>/tmp/cronout The above will execute the date command for every 4 hours like...

6. Shell Programming and Scripting

Script fails to run properly when run from CRONTAB

Hello all, I'm trying to write a script to gather and send data and it works just fine at the bash command line, but when executing from CRON, it does not run properly. My scripting skills are pretty limited and there's probably a better way, but as I said it works at the command line, but...

7. Solaris

How to run cron entry every 5 min during office hours only?

Hi I need to setuop a cron entry to run every 5 min, only in office hours (between 8:00AM to 18:00PM, I did the following: 0,5,10,15,20,25,30,35,40,45,50,55 8,9,10,11,12,13,14,15,16,17,18 * * * /home/xxx/zzz.ksh But somehow does not work. Could it be wrong?

8. Shell Programming and Scripting

Can't get my crontab to run

I'm trying to get a crontab to run, every Friday at 11am and the problem is that it isn't running at all. 0 11 * * 6 /Users/martinb/Documents/SYSADMIN/Regular-Scripts/Info-And-Backups.sh Here's a link to a screenshot of my script (I've censored my email address). Screen Shot 2017 11 03...

9. Shell Programming and Scripting

Help 'speeding' up this 'parsing' script - taking 24+ hours to run

Hi, I've written a ksh script that read a file and parse/filter/format each line. The script runs as expected but it runs for 24+ hours for a file that has 2million lines. And sometimes, the input file has 10million lines which means it can be running for more than 2 days and still not finish....

10. Shell Programming and Scripting

Run a command once in three hours

Hi All, I have a bash script which is scheduled to run for every 20 minutes. Inside the bash script, one command which I am using need to be triggered only once in two or three hours.Is there anyway to achieve this. For example, if then echo "hi" else echo "Hello" UNIX Command---once...

LEARN ABOUT OSF1

cron

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)