Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Subject: RE: cron script can awk wget file but not head/cat it Date: Fri, 9 Sep 2005 19:13:12 -0600 Message-ID: <3C46C4ED0F9B944690547357EB7F1C0F04A482@COFORTCOL2S304.agwest.one.usda.gov> From: "Pagano, Tom - Portland, OR" To: , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id j8A1DKng005387 This was exactly the problem. I'm sharing someone else's computer, so I didn't even realize those files were there (i.e. C:/bin/ is chock full of grep.exe, head.exe, sed.exe...). At the start of my script I defined my path and it worked no problem. Crisis averted, thank you! Tom --------- >From your cygcheck, you have some set of unix-like utilities in c:\bin. Check the setting of the PATH from within the cron job, as I would be willing to bet that your Cygwin bin directory is not in the path and that you're actually calling these non-Cygwin versions of those commands that have no idea what /home/tompagano is. The default install of Cygwin only modifies the PATH through the cygwin.bat file, not via the system-wide setting of PATH in the registry, so by default Cygwin is only in your path when you click on cygwin.bat to launch a bash prompt. Brian