From owner-freebsd-questions Wed Apr 7 3:54:16 1999 Delivered-To: freebsd-questions@freebsd.org Received: from woodstock.monkey.net (kronos-2-11.mdm.mkt.execpc.com [169.207.85.139]) by hub.freebsd.org (Postfix) with ESMTP id AF08214D12 for ; Wed, 7 Apr 1999 03:54:13 -0700 (PDT) (envelope-from hamilton@pobox.com) Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id B29C8E1; Wed, 7 Apr 1999 05:52:02 -0500 (CDT) To: Jamie Norwood Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Weird crontab/script problem In-reply-to: Your message of "Wed, 07 Apr 1999 01:37:21 PDT." <19990407013721.A15530@ethereal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Apr 1999 05:52:02 -0500 From: Jon Hamilton Message-Id: <19990407105202.B29C8E1@woodstock.monkey.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990407013721.A15530@ethereal.net>, Jamie Norwood wrote: } } } OK, I have a script I have written to send out some pings and record the } results. When I run it by hand, it works fine. When I put it in a crontab, it } never does anything. } } The script is simple and is as follows: } } --- } #/usr/local/bin/tcsh Is that a typo? You probably mean "#!" } ping -c 100 208.166.54.1 > /tmp/ping.`date +%m.%d.%H.%M` Try using the full path to ping, or setting the search path in your script. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message