11-15-2009
To redirect stderr (2) to whatever stdout (1) is pointing to (the two output streams get to be blended).
Last edited by Scrutinizer; 11-15-2009 at 03:03 AM..
Reason: Changed stdin to stdout (umpteenth time)
10 More Discussions You Might Find Interesting
1. Solaris
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)
Discussion started by: Negm
3 Replies
2. Shell Programming and Scripting
Can any body kindly tell me what is the purpose of 2>&1 in the following commands.
nohup ./append_import.sh 1 > import1.out 2>&1 < /dev/null &
nohup ./append_import.sh 2 > import2.out 2>&1 < /dev/null & (1 Reply)
Discussion started by: mmunir
1 Replies
3. UNIX for Dummies Questions & Answers
Hi there,
I'm using crontab to move some files every minute, but when crontab doesn't find these files it sends a message to the file "user_name" in the directory "var/spool/mail". Is it possible to "bypass" this problem?
Thanks in advance,
Giordano Bruno (1 Reply)
Discussion started by: Giordano Bruno
1 Replies
4. Fedora
Hi there,
I'm working with two servers, one with FEDORA 6 and the other one with FEDORA 7, and if I put these lines in crontab:
MAILTO=MYADDRESS@mail.com
*/1 * * * * df -h
everything works fine on FEDORA 7 , while it doesn't work on6?!?...and I find this message in the log file:
MAIL... (2 Replies)
Discussion started by: Giordano Bruno
2 Replies
5. Solaris
I have two ethernet interfaces nge0 and nge1.
An IP assigned on nge0 is 10.10.10.1/24 and on nge1 is 20.20.20.1/24. I want to make nge0 as primary interface.
My question here is,
1. Being nge0 as primary interface, if I ping to an IP 20.20.20.5, what will happen?
2. If the answer for the... (4 Replies)
Discussion started by: nthiruvenkatam
4 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have read from the book that , <> causes the file to be used as both input as well as output. Can anyone give me the scenario where <> will be useful?
Thanks (10 Replies)
Discussion started by: pandeesh
10 Replies
7. Solaris
Hi Experts,
I would like to know, what does "2>&1" do in crontab?
example:
* * * * * /export/user/home/test.sh >> /export/user/home/logtest.log 2>&1
My colleague told me the commabd 2>&1 mean to prevent crontab sending an email (sendmail on /var/mail/root) when the script failed. So, if... (5 Replies)
Discussion started by: edydsuranta
5 Replies
8. Solaris
Hello Guru's
I'm trying to take the output of solaris top command and output to a txt file every few minutes. The issue that I'm experiencing is that I can run the following:
#!/bin/bash
#
logfile="/usr/mvf/morris/top.log"
# echo... (2 Replies)
Discussion started by: littlemorris
2 Replies
9. UNIX for Dummies Questions & Answers
HI,
I am using centos 6 and finding difficultly in doing 2 below things.
1. i have a user praveen i want to allow him to create cron job of his own. so i have added his user id in cron.allow but still it is not allowing him to edit(even if i have created praveen from root user) or create his... (4 Replies)
Discussion started by: praveenkumar198
4 Replies
10. Shell Programming and Scripting
I have a script that emails me when I run it manually, but the crontab I'm using must be 'silencing' the output? Here's what I have:
*/15 * * * * /usr/src/blah.sh > /dev/null 2>&1
I don't want it to email me every time it runs, just when I run the sendmail command inside the script if the... (13 Replies)
Discussion started by: unclecameron
13 Replies
LEARN ABOUT MOJAVE
crontab
CRONTAB(1) BSD 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
The crontab utility 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 they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/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. The format of these
files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com-
ments.
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 following options are available:
-u Specify 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.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well
as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
December 29, 1993 BSD