This is the mail archive of the
mailing list for the Cygwin project.
Re: Copy to network UNC path from crontab works in non-production, not in production
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 11 May 2011 21:03:32 -0400
- Subject: Re: Copy to network UNC path from crontab works in non-production, not in production
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
On 5/11/2011 8:50 PM, CygwinNoob wrote:
Windows 2008 64-bit
I have a script that I am trying to run from cron that copies a local file
on a Windows 2008 server to a UNC path on another Windows 2008 server. It
works fine in a non-Production environment, but not in Production and I
can't figure out why. Yes, I've dutifully searched the forum and looked at
The answer is not popping out at me. What I'm doing is basically this:
cp a.a \\\\server-name\\sharename
What I get in Production is:
cp: cannot create regular file `//server-name/sharename': File exists
So what's the difference between your "Production" and "non-Production"
environments? What exactly are you doing in both environments?
FWIW, you're better off using forward-slashes for pathnames in Cygiwn
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple