I wud be posting all details, just let me know how to check who owns crontab?
---------- Post updated at 08:41 PM ---------- Previous update was at 07:41 PM ----------
Quote:
Originally Posted by methyl
Let's get some base facts.
Which Operating System?
Which Shell?
Which database engine?
What is in the script?
What is in the crontab line?
Which user did you use test from the command line?
Which user owns the crontab?
Any error messages in unix mail for the user?
1) Sun Solaris
2) Ksh shell
3) sqlplus (Oracle)
4) Code
Code for sql file:
5) Crontab Line
6 & 7 ) same user is used for both crontab and manual run
8) No error.
I am creating multiple files, all working fine, then y only spooled one is having error...... Pls Help.......!
Hi,
I trying to include a script in my crontab as user. I used "crontab -e" to include my script there but does not seem to work. If I understand correctly it is set to run at 11:20 every day, correct?
Can anybody identify any error?
<pre>
#Sun Microsystems Inc. SunOS 5.7 Generic... (19 Replies)
HI,
i am working on linux.
i have crontab problem
i wrote a small script and put it in a crontab .
but the script is not running..
i have given following way in crontab -e
02 06 * * * /bin/csh /home/vr_test.csh
but the above script is not running
please rectify my... (26 Replies)
I'm trying to get crontab to run a script, but to test crontab I tried out a very simple command: `echo bob`
here is my crontab file (I edited it by using `crontab -e`):
-----------------
#!/bin/sh
23 10 * * * echo bob
and at 10:23 every day I get a new message:
in /var/mail/a... (3 Replies)
i added to my crontab file:
* * * * * echo "hello"
it works, i receive a message into my /var/mail/username
and i receive: bob
in addition to a large text add-on
any help appreciated (1 Reply)
hi all
while using crontab -e im receiving
754 as output
im unable to add a entry in crontab
crontab -l is working fine
OS: sun5.8
can some one please assist me (4 Replies)
Dear All ,
I have .sh script wich has the following inside
getFileName=Listportfolio.txt.`date +'%Y%m%d`
ftp -n 172.10.10.1<<EOF
user xxx xxx
bin
cd /home/gbs/FTP_Script
get /home/gbs/FTP_Script/$getFileName
bye
EOF
EOF
when I run the... (3 Replies)
Hi All,
Am facing an issue while updating the crontab.Getting below error while updating the cron.
cron/tmp.XXXX5fXBR6: No space left on device
crontab: edits left in /tmp/crontab.XXXXEJX5gw
Is there any file where i need to alter using root user so that i can update the cron.
TIA... (9 Replies)
Hi to all.
Guys, i have a truble with oracle user crontab.
He work if i'm do
0-59 * * * * echo LOL> ~/test.txt
But not work if me set realy norm date
For example
14 17 28 12 * echo LOL> ~/test.txt
In 17:14 28 December .
In log file /var/adm/cron/log nothing....
Please... (3 Replies)
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)
hi all
does any on has explanation for this result
bash-3.00$ crontab -e
"/var/tmp/Ex1kayUW" No space left on device
The crontab file was not changed.
bash-3.00$ (2 Replies)
Discussion started by: osmannix
2 Replies
LEARN ABOUT DEBIAN
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)NAME
crontab - maintain crontab files for individual users (Vixie Cron)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] [ -i ] { -e | -l | -r }
DESCRIPTION
crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have
their own crontab, and though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly.
If the /etc/cron.allow file exists, then you must be listed (one user per line) therein in order to be allowed to use this command. If the
/etc/cron.allow file does not exist but the /etc/cron.deny file does exist, then you must not be listed in the /etc/cron.deny file in order
to use this command.
If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use
this command, or all users will be able to use this command.
If both files exist then /etc/cron.allow takes precedence. Which means that /etc/cron.deny is not considered and your user must be listed
in /etc/cron.allow in order to be able to use the crontab.
Regardless of the existance of any of these files, the root administrative user is always allowed to setup a crontab. For standard Debian
systems, all users may use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be used (when listing) or modified (when editing). If this
option is not given, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse
crontab and that if you are running inside of su(8) 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. See the note under DEBIAN SPECIFIC below.
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. If neither of the environment variables is defined, then the default
editor /usr/bin/editor is used.
The -i option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab.
DEBIAN SPECIFIC
The "out-of-the-box" behaviour for crontab -l is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the beginning
of the crontab when it is installed. The problem is that it makes the sequence
crontab -l | crontab -
non-idempotent -- you keep adding copies of the header. This causes pain to scripts that use sed to edit a crontab. Therefore, the default
behaviour of the -l option has been changed to not output such header. You may obtain the original behaviour by setting the environment
variable CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.
SEE ALSO crontab(5), cron(8)FILES
/etc/cron.allow
/etc/cron.deny
/var/spool/cron/crontabs
There is one file for each user's crontab under the /var/spool/cron/crontabs directory. Users are not allowed to edit the files under that
directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct
crontabs will be written there. This is enforced by having the directory writable only by the crontab group and configuring crontab com-
mand with the setgid bid set for that specific group.
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
A fairly informative usage message appears if you run it with a bad command line.
cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing the newline, cron will
consider the crontab (at least partially) broken and refuse to install it.
AUTHOR
Paul Vixie <paul@vix.com> is the author of cron and original creator of this manual page. This page has also been modified for Debian by
Steve Greenland, Javier Fernandez-Sanguino and Christian Kastner.
4th Berkeley Distribution 19 April 2010 CRONTAB(1)