02-08-2007
We might have some ideas if you show us the script.
But some options are:
- You say the script produces output, where is this output send? To a file or to the screen? If it is the screen the script will not work because there is no tty attached to t.
- A cron job runs by default with a very limited PATH environment variable. So if you don't define PATH inisde your script correctly, or use all commands with their full pah name, it could be that 1 or more commands cannot be located and therefore result in an error, which cause your script to terminate.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: matrixmadhan
3 Replies
2. Shell Programming and Scripting
Hello,
I am trying to schedule a job to run every 15 minutes from 7am to 5:30pm. Could someone show me the syntax for this?
Thanks. (1 Reply)
Discussion started by: bestbuyernc
1 Replies
3. UNIX for Advanced & Expert Users
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)
Discussion started by: Sowser
4 Replies
4. AIX
Hi. I'm new to AIX and I need to create a crontab entry to run a script every first 5 business days of the month? please help. (2 Replies)
Discussion started by: udelalv
2 Replies
5. Solaris
How to set the crontab entry for every other Friday?
Regards,
Raj (1 Reply)
Discussion started by: rajip23
1 Replies
6. Solaris
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)
Discussion started by: jaweedak
3 Replies
7. UNIX for Dummies Questions & Answers
What should be the crontab entry for a script:
to run at 3:00 AM EST Sun, Mon, Tue, Wed, Thu, Fri (3 Replies)
Discussion started by: proactiveaditya
3 Replies
8. Solaris
hi
i am new in solaris. i am accessing server through putty. i could not add entry in crontab.
i have given "crontab -e" for add a new entry. It is not coming. what parameter i have to set for getting crontab -e
thanks (1 Reply)
Discussion started by: sunnybee
1 Replies
9. UNIX for Dummies Questions & Answers
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)
Discussion started by: Me XMan
5 Replies
LEARN ABOUT OPENDARWIN
script
SCRIPT(1) BSD General Commands Manual SCRIPT(1)
NAME
script -- make typescript of terminal session
SYNOPSIS
script [-a] [-k] [-q] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an
interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1).
If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command ... is given, script will run the specified command with an optional argument vector instead of an interactive shell.
Options:
-a Append the output to file or typescript, retaining the prior contents.
-k Log keys sent to program as well as output.
-q Run in quiet mode, omit the start and stop status messages.
-t time Specify time interval between flushing script output file. A value of 0 causes script to flush for every character I/O event. The
default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-d (if
ignoreeof is not set) for the C-shell, csh(1)).
Certain interactive commands, such as vi(1), create garbage in the typescript file. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
ENVIRONMENT
The following environment variable is utilized by script:
SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most
shells set this variable automatically).
SEE ALSO
csh(1) (for the history mechanism).
HISTORY
The script command appeared in 3.0BSD.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when in a raw mode where the program being run is doing manual echo.
BSD
June 6, 1993 BSD