Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Having Problem with crontab command Post 2660 by Peterh on Tuesday 29th of May 2001 05:08:00 AM
Old 05-29-2001
Smilie Hi Arunava

I have my crontab like this

17 09 * * 1-5 /mydir/myshell.sh

First the minutes then the hours.This how it works on my true64unix.

But don't forget the full path..

Peterh
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with Crontab

I have a problem with crontab. I made a class file name Mailer.class. When I run it at command line like this: $ java Mailer It runs very well and I got the email. But If I put it in a crontab line like this: 30 11 * * * java Mailer It doesn't work. Every time the cron job... (5 Replies)
Discussion started by: qhuynh
5 Replies

2. Shell Programming and Scripting

Crontab problem

Hi all, I made few changes to the script (under the directory mentioned in crontab) scheduled under crontab and the problem is that crontab doesnt pickup those changes and somehow runs the old copy of the script from somewhere. Any help would be appreciated. (8 Replies)
Discussion started by: vinoo128
8 Replies

3. UNIX for Dummies Questions & Answers

Crontab problem

I have script which uses "for loop" for doing some activity. Inside for loop i have extracted some data and redirecting it to HTML file using "echo" command. When i run this script manually it runs fine and appends the data in the HTML file. However, when I am croning this script for every 5 min... (2 Replies)
Discussion started by: manandixit
2 Replies

4. Linux

crontab problem

Hello, I have this in the crontab 30 2 * * * /bin/sh /home/abc but in the log it looks run below Jan 27 08:30:01 localhost crond: (root) CMD (/bin/sh /home/abc how could this happen? I logged in with root user,I use root user's crontab. Kind Regards (9 Replies)
Discussion started by: sunsail
9 Replies

5. UNIX for Advanced & Expert Users

crontab problem

hi.. i have a program (tf.sh), and i want what it runs automatically with a "lapsus" of 2 hours. (1,3,5,7,9,11,13,15,17,19,21,23 hrs.) i know what i have to do it using crontab, but i donīt know how to do it. i have the next idea, but the problem is what it doesnīt run on my server... (11 Replies)
Discussion started by: DebianJ
11 Replies

6. AIX

Problem with crontab

Hi, Can anyone let me know the functionality of the following command in Unix crontab ;l Thanks, Wajith.M (3 Replies)
Discussion started by: Wajith
3 Replies

7. Shell Programming and Scripting

Crontab command substitution problem

Hi all, I am using Ubuntu 8.04 Linux. I have a cron job entry to run a shell script at a scheduled time. This script has a X application to be launched. As cron does not pick already exported environment variables and it runs in a separate environment, I need to export the DISPLAY variable to... (9 Replies)
Discussion started by: royalibrahim
9 Replies

8. Solaris

Crontab Problem

Dear All I have machine with SunOS APP5a 5.9 Generic_122300-19 sun4u sparc SUNW,Sun-Fire With crontab like this : 59 23 * * * /home/lng/script/move_and_compress_logs_update.sh But that crontab cannot running at that time. I run my script by manually, the result is fine. What must I check at... (5 Replies)
Discussion started by: mbah_jiman
5 Replies

9. Shell Programming and Scripting

Crontab problem

Hi One shell script is running fine when I am running it through command line. However the same thing is not working when I am trying through cron. Basically when I debugged I found when I am running it throuh ssh terminal ( putty) it's getting loading the profile file properly but... (7 Replies)
Discussion started by: Anupam_Halder
7 Replies

10. Shell Programming and Scripting

Problem with running the "autorep" command via crontab

Hi, The user "MadeInGermany" tried to help on the below post by saying "This has been asked before; see the links below. Get your current LD_LIBRARY_PATH and redefine that in your ksh script! " Thanks for the help. but this did not help. And my post got locked. I can't reply on my previous... (5 Replies)
Discussion started by: girish1428
5 Replies
CRONTAB(1)							   User Commands							CRONTAB(1)

NAME
crontab - maintains crontab files for individual users SYNOPSIS
crontab [-u user] file crontab [-u user] [-l | -r | -e] [-i] [-s] crontab -n [ hostname ] crontab -c DESCRIPTION
Crontab is the program used to install, remove or list the tables used to serve the cron(8) daemon. Each user can have their own crontab, and though these are files in /var/spool/, they are not intended to be edited directly. For SELinux in MLS mode, you can define more crontabs for each range. For more information, see selinux(8). In this version of Cron it is possible to use a network-mounted shared /var/spool/cron across a cluster of hosts and specify that only one of the hosts should run the crontab jobs in the particular directory at any one time. You may also use crontab(1) from any of these hosts to edit the same shared set of crontab files, and to set and query which host should run the crontab jobs. Running cron jobs can be allowed or disallowed for different users. For this purpose, use the cron.allow and cron.deny files. If the cron.allow file exists, a user must be listed in it to be allowed to use cron If the cron.allow file does not exist but the cron.deny file does exist, then a user must not be listed in the cron.deny file in order to use cron. If neither of these files exists, only the super user is allowed to use cron. Another way to restrict access to cron is to use PAM authentication in /etc/security/access.conf to set up users, which are allowed or disallowed to use crontab or modify system cron jobs in the /etc/cron.d/ directory. The temporary directory can be set in an environment variable. If it is not set by the user, the /tmp directory is used. OPTIONS
-u Appends the name of the user whose crontab is to be modified. If this option is not used, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) may confuse crontab, thus, when executing commands under su(8) you should always use the -u option. If no crontab exists for a particular user, it is created for him the first time the crontab -u command is used under his username. -l Displays the current crontab on standard output. -r Removes the current crontab. -e Edits the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automatically. -i This option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab. -s Appends the current SELinux security context string as an MLS_LEVEL setting to the crontab file before editing / replacement occurs - see the documentation of MLS_LEVEL in crontab(5). -n This option is relevant only if cron(8) was started with the -c option, to enable clustering support. It is used to set the host in the cluster which should run the jobs specified in the crontab files in the /var/spool/cron directory. If a hostname is supplied, the host whose hostname returned by gethostname(2) matches the supplied hostname, will be selected to run the selected cron jobs subsequently. If there is no host in the cluster matching the supplied hostname, or you explicitly specify an empty hostname, then the selected jobs will not be run at all. If the hostname is omitted, the name of the local host returned by gethostname(2) is used. Using this option has no effect on the /etc/crontab file and the files in the /etc/cron.d directory, which are always run, and considered host-specific. For more information on clustering support, see cron(8). -c This option is only relevant if cron(8) was started with the -c option, to enable clustering support. It is used to query which host in the cluster is currently set to run the jobs specified in the crontab files in the directory /var/spool/cron , as set using the -n option. SEE ALSO
crontab(5), cron(8) FILES
/etc/cron.allow /etc/cron.deny STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. DIAGNOSTICS
An informative usage message appears if you run a crontab with a faulty command defined in it. AUTHOR
Paul Vixie <vixie@isc.org> Colin Dean <colin@colin-dean.org> cronie 2012-11-22 CRONTAB(1)
All times are GMT -4. The time now is 09:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy