Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 2 Sep 2003 10:48:22 -0400 (EDT)
From: Louis-Luc Le Guerrier <leguerri AT IRO DOT UMontreal DOT CA>
To: cygwin AT cygwin DOT com
Subject: RE: Need help: cron jobs can't access network drives.
Message-ID: <Pine.LNX.4.44.0309021031200.21103-100000@vor.iro.umontreal.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MailScanner-DIRO: Found to be clean


Hello,
I have tried Universal Name Convention path as well, and I still can't
access the network drives, even with UNC paths inside the script ran by
'cron'. The same script invoked  manually accesses net drives of course.

I have looked at "www.denicomp.com/faq.htm#Q21" and understand partially
what they mean to do, but they don't explicitly explain how to perform
the tasks in Windows.

I also noticed the 'id' command on the Cygwin shell gives "Administrator"
as user name when invoked manually. I also included 'id > tstfile' into
a 'cron' job to send the output of 'id' while in a cron, and it also
states "Administrator" is the user. I set up a password to the Windows
Administrator account, and it's the one I log in. cron still fails to
access network drives even though Administrator has a password and
I'm trying it with UNC paths. 

I'm still puzzled, and stuck unable to access network drives.

Anyone can share a clearer procedure of what to do, or an example?

Thanks in advance.

Louis-Luc



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/