From: Dermot Paikkos (dermot@sciencephoto.com)
Date: Tue Jul 22 2003 - 09:31:12 EDT
I thought i'd simmarise quickly as the number of replies is getting
overwhelling :-).
I mis-read UNIX Power tools book. I am missing a > before the file.
So chown -R images /images/hires/*.jpg > /dev/null 2>&1 works and
chown -R images /images/hires/*.jpg /dev/null 2>&1 is missing a ">"
before the file.
Thanx to massimo,paul sand, paul lamadeleine, robert binkerly,
martin adolfsson, lindsay wakeman, chris ruhnke and galen johnson.
======= Orginal message ==
Hi Managers,
TRU64 5.1
I have tried to redirect the output from cron to /dev/null for a
couple of jobs that run frequently during the day. I can't seem to get
it to work and I am being bombarded with mails that are of no use.
I have tried the following in the root crontab:
chown -R images /images/hires/*.jpg >& /dev/null
chown -R images /images/hires/*.jpg /dev/null 2>&1
Neither have worked. I am still getting the following message when
there is no file to chown. Is there some way to avoid this? Thanx. Dp.
chown: /images/hires/*.jpg: No such file or directory
*************************************************
Cron: The previous message is the standard output
and standard error of the following crontab command:
chown -R images /usr2/images/dump_hires/*.jpg /dev/null 2>&1
------- End of forwarded message -------
~~
Dermot Paikkos * dermot@sciencephoto.com
Network Administrator @ Science Photo Library
Phone: 0207 432 1100 * Fax: 0207 286 8668
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:28 EDT