I have added the script entry into crontab by using crontab -e.
But its not working yet.
Note: When i was added the script by the time I have faced issue as below
1) If I use crontab -l then i got cant open the script.
solved: I have open the crontab -l then pressed del key only .
2) If i open the crontab -e then I got 0 ,
Solved: I have export the vi EDITOR then ok now.
After that I have opened then i got 96 number.
I dont know How can i solve the issue.
Please advice on this.
Thanks,
Mani
Moderator's Comments:
5 times ignored notices to use code tags from different moderators.
Last edited by zaxxon; 09-14-2011 at 07:24 AM..
Reason: code tags
hi all
how to schedule a cron job running on last day of every third month at
12 midnight
will the following work
0 0 30,31 3,6,9,12 * <required file>
thanks (3 Replies)
Sometimes cron really upsets me and I cant figure out these types of wierd dates, but how do I get cron to run something on every other sunday? I am running Solaris 8.
-S (4 Replies)
Hi Everyone , have a nice day
given below is the line i have added in crontab
* * * * * /Rauf/script2.sh
intended to run this script after every minute , when i run this script manually it runs fine and produces output , but after adding it to crontab ( like given above ) , it doesnt work
... (5 Replies)
Hi,
i need to setup a cronjob that has will execute iostat command from morning to evening time.
for instance the timing has will be like this.
8:00 A.M -- 6:00P.M
how to define this entry in crontab
Regards (3 Replies)
Hi
I have a perl script which used 'glance' command to return all the processes with the thread count.
It is working fine when it is executed as a command, but as a crontab entry, the perl script is not getting executed.
thdcnt.pl
#!/usr/bin/perl
my $cmd=`glance -bootup -adviser_only... (1 Reply)
Hi I am trying to test the crontab entry by setting time as below ( set ahead more than 3min before saving the cron)
crontab entry:
30 15 1-27 * * && (cd /scripts;./script.csh.prod.UAT /dev/null 2>&1)
But this is not working, but below one is working.
30 15 1-27 * * (cd... (1 Reply)
Is this the correct entry to touch a file on 6/6 5AM?
00 05 06 06 * touch /support/home/.no_copy Please use next time code tags for your code and data (5 Replies)
I have put a cron entry in oracle user for taking hot backup every wednesday@ 2.30 AM and have given the cron entry
30 02 * * 3 /u01/vijay/hotbackupcron 2>&1 >> /u01/vijay/hotbackup.log
also find below the script inside hotbackupcron, i have put in env variables as well
... (13 Replies)
Discussion started by: vijaymec50
13 Replies
LEARN ABOUT NETBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)NAME
crontab -- maintain crontab files for individual users (ISC Cron V4.1)
SYNOPSIS
crontab [-u user]
crontab [-elr]
DESCRIPTION
crontab is the program used to install, deinstall, or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have their
own crontab, and though these are files in /var/cron, they are not intended to be edited directly.
If the /var/cron/allow file exists, then you must be listed therein in order to be allowed to use this command. If the /var/cron/allow file
does not exist but the /var/cron/deny file does exist, then you must not be listed in the /var/cron/deny file in order to use this command.
If neither of these files exists, depending on the compiled in settings, only the super user will be allowed to use this command, or everyone
will be allowed to use this command. On NetBSD everyone is allowed to use this command.
The default maximum size for a crontab is 256 kilobytes, but this may be changed for all users on the system by putting the desired maximum
size (in bytes) in the /var/cron/maxtabsize file.
If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines
``your'' crontab, i.e., the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running
inside of su(1) you should always use the -u option for safety's sake.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given.
The -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit 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.
FILES
/var/cron/allow Optional list of users that are allowed to use crontab.
/var/cron/deny Optional list of users that are disallowed to use crontab.
/var/cron/maxtabsize Maximum size of crontab files. Defaults to 256 kilobytes.
/var/cron/tabs/ Directory containing the individual user crontab files, named after the user.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO crontab(5), cron(8)STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). This new command syntax differs from previous versions of Vixie Cron, as well
as from the classic Version 3 AT&T UNIX syntax.
AUTHORS
Paul Vixie <vixie@isc.org>
BSD May 6, 2010 BSD