There is no tty, no /dev/tty, no controlling terminal. You can create one in several ways, like ssh -tt and expect, but usually one does not want terminal output from a cron job.
You have to build the environment manually, and if you were not careful writing your ~/.profile, it may want a tty. Without the usual PATH, LD_LIBRARY_PATH, etc. many apps fail.
Execuatble scripts should be set up according to man exec to run under the right interpreter. Cron will call scripts using sh, and if you lack exec permissions or first line is not:
then you are in trouble.
I often test run cron script lines using something like:
(no terminal, called from sh).
Hello,
I'm stuck and confused as to why when I execute things form the command line it works but when in a script it doesn't.
My script:
### creating a lock on the console
touch /var/run/console.lock
chmod 600 /var/run/console.lock
echo "$User" >>... (2 Replies)
Howdie everyone...
I have a shell script RemoveFiles.sh
Inside this file, it only has two commands as below:
rm -f ../../reportToday/temp/*
rm -f ../../report/*
My problem is that when i execute this script, nothing happened. Files remained unremoved. I don't see any error message as it... (2 Replies)
Hey there, I'm a total newbie unix guy here and just picking this stuff up. Have a very small script I put together that works fine from the command line but not once I put it in a cron job. Searched and found this thread and am wondering it it has something to do with setting variables, though the... (7 Replies)
I have a script which runs fine through command line, but doesn't run through cron. There are some variables which are set by the .profile file which are used by the script. Is it that cront does not pick these variables.
$/export/home/rahul/bin/createfile.sh >>... (3 Replies)
Hi, I'm new to these forums, and I'm hoping that someone can solve this problem...
To make things short:
I have DD-wrt set up on a router.
I'm trying to run a script in CRON that fetches the daily password from my database using SSH.
CRON is set like so(in web interface):
* * * *... (4 Replies)
Hi all,
I have a script that can be run via cron or via the command line.
Is there any way that I can place something on the script to be able to distinguish/differentiate whether the script was run via a user in the command line or whether it was run from the cron? (3 Replies)
In my cron thare is a line like
24 11 * * * /usr/batch/bin/abc.sh > /usr/batch/log/abc.log 2>&1
along with other entries. I want to comment out this line through a shell script. My local variable 'line'ontains the full entry (i.e. 24 11 * * * /usr/batch/bin/abc.sh > /usr/batch/log/abc.log... (4 Replies)
Hi, I have a script that seems to run to completion when in the command-line, but when it is run using the cron, it seems to time out.
They both start and run fine, but on the CRON it stops prematurely.
The script hits an API every few seconds and grabs data.
Does anyone have any idea on... (4 Replies)
Hi
I have a text file (Input.txt) with two column entries separated by tab as given below:
aaa str1
bbb str2
cccccc str3
dddd str4
eee str3
ssss str2
sdf str3
hhh str1
fff str2
ccc str3
.....
.....
..... (1 Reply)
0
I have a script(main.sh) which calls another script(Get_Files.sh) and gets a value in a variable like the below:
File_to_Refresh="$(sh /Aug/work/Get_Files.sh /Aug/Work/Universal_File.txt)"
Now I have to schedule the script main.sh for 3 different files i.e. the Universal_File.txt with 3... (2 Replies)
Discussion started by: bhartiya007
2 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