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 Message-ID: <3500515B75D9D311948800508BA37955950569@EX-LONDON> From: Vince Hoffman To: =?iso-8859-1?Q?=27Sven_K=F6hler=27?= , djordan AT augustmail DOT com Cc: cygwin AT cygwin DOT com Subject: RE: WinXP upgrade breaks cron mapping Date: Fri, 2 Aug 2002 15:34:39 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g72EZFO06074 maybe the smb client would be useful here ? http://main.mswinxp.net/~lpackham/smbclient/ -----Original Message----- From: Sven Köhler [mailto:skoehler AT upb DOT de] Sent: 02 August 2002 15:00 To: djordan AT augustmail DOT com Cc: cygwin AT cygwin DOT com Subject: Re: WinXP upgrade breaks cron mapping > I realize the cron is running under SYSTEM account and that's why I have to > manually map drives within my cron scripts. Is there any knowledge on the > differences with XP and NT which might explain why mapping the drives with > my own NT id would not work as they did prior to upgrading to XP? I have > the same permissions on the remote server as I always had. as far as i know the SYSTEM-Account cannot acces any network drives. you should perhaps su to your userid - altough this should already be done by cron itself (if the cronjobs are not scheduled to run as root). hope it helps. Sven -- 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/ -- 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/