The crontab does not run the login files like .profile; certainly an important piece of environment is missing.
A brute force copy of your current environment:
and have the following command in crontab
with the correct path of course.
Does any one knows a work around for the crontab bug when connecting using ssh to a Solaris 8 system?
When you submit a crontab job through a ssh session, the job will not be executed, SunSolve has reported no fixing patches? (3 Replies)
Apologies if this has been mentioned elsewhere, my search skills may be lacking somewhat today.
I have a script that does the following (as a test):
find . -name "*.txt" -exec file {} \; >>$sFullFilePath
Now, the variable is set up up correctly in the script too. When I run the script... (1 Reply)
foreach x ( *.foo)
echo "move file?"
set move=$<
if($move == y) then
echo "enter new pathname:"
set path=$<
mv $x $path/$x
endif
end
ok guys, im creating this script so i can move files with *.foo extensions and *.bar... (6 Replies)
Hi all,
I'm having this scenario which for the moment I cannot resolve. :(
I wrote a script to make a dump/export of the oracle database. and then put this entry on crontab to be executed daily for example.
The script is like below:
cat /home/oracle/scripts/db_backup.sh
#!/bin/ksh
... (3 Replies)
Why is the result of this command off (or less) by one hour
date --date "1979-10-26 +54 hours" +%Y%m%d%H
The result is
1979102805
It actually should be
1979102806
It does it with adding minutes as well and only occurs on Oct. 26, from what I can tell. What's going on here? (9 Replies)
Hello,
i have page domain.com/form.php
the form fields on form.php are named:
name=ipaddress
name=port
and submit button is named: submit
i want to ask how the linux command will look like to submit the form filled with:
ipaddress: 127.0.0.1
port: 80
I tried various curl and... (5 Replies)
my problem is this: when I run a script from the command line it works but returns a failure if I run it from crontab.
Basically I wanted to send a file to hdfs,
I thought it was related to the fact that crontab do not know the path to hdfs so I put the full path but it still does not work: here... (16 Replies)
Discussion started by: beautymind
16 Replies
LEARN ABOUT REDHAT
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)NAME
crontab - maintain crontab files for individual users (V3)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] { -l | -r | -e }
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, they are not intended to be edited directly.
If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but
the deny file does exist, then you must not be listed in the 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 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(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.
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.
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
A fairly informative usage message appears if you run it with a bad command line.
AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 29 December 1993 CRONTAB(1)