Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Fri, 14 Feb 2003 13:23:15 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: "Larry Hall (RFK Partners, Inc.)" cc: Juraj.Lenharcik@t-systems.com, Subject: Re: cron and network drives In-Reply-To: <3E4D069A.3070407@rfk.com> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 14 Feb 2003, Larry Hall (RFK Partners, Inc.) wrote: > Juraj.Lenharcik@t-systems.com wrote: > > Hi, > > > > is there a possibility to reach the network drives with cron. My > > scripts work fine and can reach the network drives when I execute them > > from command line. With cron there is no effect. Is there a > > possibility to copy some file from cygwin to a network (windows) > > drive, without modifieing the network computer (like ssh, etc.)? > > > > Can I get cron to work with network drives? > > Only if you make them publically accessible. > > We need an entry in the FAQ about the inaccessiblity of network shares > from Cygwin run services. FWIW, it's in the User's Guide: Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! -- /usr/games/fortune -- 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/