This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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
Attachment:
cygcheck-local_login.txt
Description: cygcheck-local_login.txt
-- 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/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |