On Fri, 17 Aug 2007, Linda Walsh wrote:
Corinna Vinschen wrote:
> Larry is right, of course, but I make a wild guess, nevertheless:
>
> CYGWIN=nosmbntsec
---
Assuming you mean having that string in the CYGWIN env var,
unfortunately, this is not the case.
See <http://cygwin.com/cygwin-ug-net/using-cygwinenv.html> -- nosmbntsec
is the default. You need to turn it on to get ntsec functionality on
remote drives.
As for including cygcheck, I don't have a problem doing that
when necessary, but I prefer to check that it's not some "braino", or
that it is a "real" problem before attaching a full cygdump.
How will we know if it's a real problem unless you include the cygcheck
output?
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Belief can be manipulated. Only knowledge is dangerous. -- Frank Herbert
--
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/
