08-24-2008
That's the idea, yes. To be on the safe side, perhaps you can start by redirecting to a real file, instead of /dev/null, and check after the job completes that the file doesn't contain useful information. If the job is a shell script (or, for that matter, a binary that you have the source code for), it might be a useful exercise to change it so it doesn't emit spurious output, in keeping with a great Unix design principle. Maybe there could be a separate --quiet option for this.
In order to be able to test this without waiting for cron to kick in, and also to keep your crontab simple, you might want to create a wrapper script which sets up the redirections etc, and invoke that from your crontab instead of the real thing.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am running a script where i need to run another command in a particular folder which I do not have access so I need
to login as su to that folder and run that script...what are the options I need so that I
can skip interactive mode ..here is what I tried..
#! /usr/bin/sh... (2 Replies)
Discussion started by: mgirinath
2 Replies
2. Solaris
Hi there
I get the following message im my messages file 2 or 3 times a second
Dec 4 11:44:18 my-box in.timed: connect from localhost
I would like to stop in.timed from logging to syslog altogether as this message is filling up my disk.
I dont want to stop daemon.info altogether... (0 Replies)
Discussion started by: hcclnoodles
0 Replies
3. Solaris
Hello
One of our applications initiates an ftp logon to itself twice every second ...(to check some files or something im not sure) but every time it does this it logs an entry into the wtmpx database, this file is now getting absolutely huge and whilst I know that I could implement some type of... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
4. Shell Programming and Scripting
Hi, I have googled for quite some time and couldn't able to get what exactly I am looking for.. My query is "how to stop a shell script which is running inside a remote server, using a script"??? can any one give some suggestions to sort this out. (1 Reply)
Discussion started by: mannepalli
1 Replies
5. Shell Programming and Scripting
Hi All,
Sorry if it is a duplicate post. I have not got any reference about this anywhere.
I looked at the posts described in SSH - Passing Unix login passwords through shell scripts - Linux / UNIX Forum and it helped me till the point to connect to the host and executing the basic commands.... (3 Replies)
Discussion started by: RSC1985
3 Replies
6. Shell Programming and Scripting
Hi everyone,
I have this problem with a script I'm writting. I want to execute a code running in the background several times through a script. I am writting it like that
parent_script
for a in 1 2 3 4 5
do
exec test -n $a
done
What I want to do is when parent_script is killed,... (0 Replies)
Discussion started by: geovas
0 Replies
7. Shell Programming and Scripting
I am trying to write a script that can be called by other scripts to print output to a log. I also want to be able to rotate the log file for this script with a max of 5 logs files. This is what I have so far:
#/bin/ksh
. /taipso75/scripts/IPSM_run_profile.sh*
log=${IPSM_HOME}/log
(
echo... (1 Reply)
Discussion started by: Dougj75
1 Replies
8. Web Development
A Gbytes long log
/var/log/apache2/access_log
causes my question: How to stop my IP logging (just because of frequent AJAX/setTimeout).
As config:
SetEnvIf Remote_Addr "ip\.ip\.ip\.ip" dontlog
CustomLog /var/log/apache2/access_log common env=!dontlog
In
/etc/apache2/httpd.conf ... (0 Replies)
Discussion started by: Xcislav
0 Replies
9. Linux
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
10. Linux
When I do "set -n" or "set -o noexec" the shell doesn't do what it sould.
Infact if I check:
$: set -o
....
noexec off
....
f
...instead I can set normally the other option.
Who Knows what could be up? (2 Replies)
Discussion started by: flaviofachin
2 Replies
SCRIPT(1) BSD General Commands Manual SCRIPT(1)
NAME
script -- make typescript of terminal session
SYNOPSIS
script [-akq] [-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.
The following options are available:
-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
January 22, 2004 BSD