[vox-tech] STDOUT and /dev/null
I've got some scripts which run every five minutes via cron. The crontab entry looks like this: */5 * * * * wget -q http://our.server.com/admin/cron.php /dev/null 21 As I understand it, this should be directing any output from cron.php to /dev/null. It doesn't, however, and my root directory fills up very quickly with output files from the script. Am I missing something here? -- Richard S. Crawford http://www.mossroot.com That which does not kill me makes me stranger. --Llewellyn ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] STDOUT and /dev/null
Richard S. Crawford wrote: */5 * * * * wget -q http://our.server.com/admin/cron.php /dev/null 21 As I understand it, this should be directing any output from cron.php to /dev/null. It only redirects standard output and standard error. It doesn't prevent wget from creating new files. Wget's normal behavior is to create a file to save the downloaded data. Redirecting standard output or standard error won't change that. Wget has a -O option to control the name of the file that the downloaded data is written to. Either of these should do what you want: wget -q -O - http://our.server.com/admin/cron.php /dev/null 21 wget -q -O /dev/null http://our.server.com/admin/cron.php /dev/null 21 ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Fwd: RE: [vox-tech] bash: ls: command not found
[EMAIL PROTECTED] tried to send this to vox-tech, but is not subscribed to the list. (I'm Cc'ing him or her.) This looks like it's in response to this vox-tech thread from November 2002: http://lugod.org/mailinglists/archives/vox-tech/2002-11/msg00092.html FWIW, the original poster (Joseph Karalius) resolved the issue: It was a path environment variable that got changed during a program configuration. Problem is fixed. - Forwarded message from [EMAIL PROTECTED] - The attached message has been automatically discarded. Date: Tue, 28 Feb 2006 21:52:09 +0800 From: [EMAIL PROTECTED] Subject: To: vox-tech@lists.lugod.org bash: ls: command not found This is a new workstation that we got from our IT department and I've been able do get around on it before... What do I need to do to fix this? Thanks in advance, Joey I have the same problem, could you help me? thank a lot. - End forwarded message - -- -bill!Tux Paint 2006 wall calendar, [EMAIL PROTECTED]CDROM, bumper sticker apparel http://www.newbreedsoftware.com/ http://www.cafepress.com/newbreedsw ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: Fwd: RE: [vox-tech] bash: ls: command not found
On Tue, Feb 28, 2006 at 11:43:25AM -0800, Bill Kendrick wrote: bash: ls: command not found This is a new workstation that we got from our IT department and I've been able do get around on it before... What do I need to do to fix this? Thanks in advance, Joey I have the same problem, could you help me? thank a lot. Have you checked to see if your problem was the same as the original poster's? Please give us the results of the following command lines (after subscribing so we can receive further mails from you): $ echo $PATH $ type ls $ which ls $ whereis ls $ /bin/ls -- Micah J. Cowan [EMAIL PROTECTED] ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
