11-22-2002
The -v option you have added to crontab entry may be doing that.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
There is this script I'd like to put into cron, but it asks for date verification. It'll prompt you to press enter to continue. Usually, 100% of the time the dates are ok, so is there a way to run this script in cron and bypass the "enter" prompt? (3 Replies)
Discussion started by: NycUnxer
3 Replies
2. Shell Programming and Scripting
I have the following script (trapsize) that checks a file size on my syslog server, and if the file is gt 6g, it will mail an alert to the admin for inspection. The following works like a champ when I execute ./trapsize logged in as root user using bash shell.
FILESIZE=$(ls -l /opt2/fwsm/fwsm... (3 Replies)
Discussion started by: altamaha
3 Replies
3. Shell Programming and Scripting
Hi
I have an FTP script, which ftp's the files from one unix box to another box.
It works from the command when I Issue > ksh ftp.ksh
when I schedule it in CRON, it is not being executed automatically.
Any thoughts please
Thanks
Ravi. (4 Replies)
Discussion started by: ravi.balley
4 Replies
4. Shell Programming and Scripting
Hi all, I have a script running on a Solaris 8 box and the first thing it does it check which user is executing it;
if ; then
echo "This script must be run as testuser" 1>&2
exit 1
fi
This works fine when manually running the script however when adding into that users' crontab it... (1 Reply)
Discussion started by: JayC89
1 Replies
5. Solaris
Hi,
I''ve made a script that's running fine from the command line but when running from cron it encounters the following issue:
/tmp/tstscript/testfail.ksh: typeset: not found
I've searched in Google and couldn't find anything, here's the beggining of the script (I can post the rest if... (4 Replies)
Discussion started by: Cvg
4 Replies
6. Shell Programming and Scripting
Hello All,
I am running the below script.when i am running from shell or terminal its running fine but running using cron its not working.
################################
b36376 27 % cat make_nis_account_ankit.sh
#!/bin/ksh
... (2 Replies)
Discussion started by: ajaincv
2 Replies
7. Shell Programming and Scripting
Hi Guys,
I do have a shell script that I scheduled to run via the cron but when the script don't run.
But when I run the script manually it does run perfectly...
What might be the problem?
Thanks. (1 Reply)
Discussion started by: Phuti
1 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I am running a script thorugh cron which is given below.
this script is not doing its defined job through cron ,files are still in unzipped state.
But when i run this script as ./script.sh it gets executed fine and does all that is required.
also when i run thi script as sh... (2 Replies)
Discussion started by: Jcpratap
2 Replies
9. Shell Programming and Scripting
Hi All,
I am running the below shell script through cron and surprisingly it gives different output
$uname -a
Linux 2.6.18-194.3.1.7.3.el5xen #1 SMP Fri Jul 30 00:08:45 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
$ echo $SHELL
/bin/bash
shell script:
cat sar_cpu.sh
#!/bin/bash
... (10 Replies)
Discussion started by: a1_win
10 Replies
10. Shell Programming and Scripting
Hi All,
I have a script which is running fine while triggered manually, However if I placed
in crontab it throwing an error.
#!/usr/bin/ksh
set -vx
lc=1
st_date=$(`date "+%Y%m%d"`)
LOGFILE=/home/transfer.log.$st_date
file="/home/OM_WF.log.$st_date"
Manual run -
lc=1
+ lc=1... (4 Replies)
Discussion started by: nag_sathi
4 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