Cygwin can't write to CIFS... but cmd.exe *can*

[Scott Prive]

If one is authenticated against a remote CIFS share (Linux), should there be a difference in "permissions" between Cygwin and CMD.EXE?

Example:
After authentication/mount (via net use), I try `echo "foo" >myfile.txt`

In the Cygwin shell, this fails and I get a 0-byte file.
If I start CMD.EXE from the same shell, it works in the CMD processor.

Could someone please explain the inconsistency? 

If not, suggestions for workaround ARE welcome (at a higher level I'm working off a Perl script but I reproduced the above in bash using just 'echo').

To eliminate sshd issues, I am running things "locally" (using WinVNC to export my display).

-Scott
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygcheck-local_login.txt
URL: <http://cygwin.com/pipermail/cygwin/attachments/20021014/7bd08804/attachment.txt>
-------------- next part --------------
--
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/