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 From: "Paul Derbyshire" To: cygwin AT cygwin DOT com Date: Mon, 29 Jul 2002 22:08:58 -0400 MIME-Version: 1.0 Subject: Cron problem Reply-to: derbyshire AT globalserve DOT net Message-ID: <3D45BCFA.10205.5BFFFC3A@localhost> Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body What with the big directory names debate and the big ctrl-V debate it seems the cron problem thread has slipped through the cracks. The last thing I discovered was that it seems to be invoking djgpp's rm and mv and not Cygwin's. DJGPP is installed and in the Windows PATH. However, the Cygwin PATH starts with /usr/local/bin:/usr/bin:/bin so to Cygwin programs Cygwin's rm should be selected instead. Indeed, "which rm" prints "/usr/bin/rm" from the Cygwin bash prompt. Why, then, is cron using the wrong rm (and mv)? AFAICT this really is the cause of the failure. It wgets the file but fails to move it to the desktop because the DJGPP mv doesn't understand cygdrive. I imagine assigning PATH inside my crontab to prepend /usr/bin would fix it. However this smells like a crock to me -- it'd treat the symptoms but not whatever problem (cron misconfiguration?) is causing them. I know it's not the ideal solution because if this were a genuine multiuser system with multiple cygwin users set up, every one of them would have to make the same edits in their crontabs, and there just has to be a centralized way to do it instead. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/