Mail Archives: cygwin/2002/06/25/09:42:12
The SYSTEM user does not have access to network drives. You might try
giving it *all* NT rights, but that could be dangerous. And even then it
might not be able to access the drives for some reason that I am unaware
of the mechanics of but is unsurmountable. You won't be able to write
directly to network drives as the SYSTEM user, you won't be able to rsh
to other machines as the SYSTEM user either if network drives are
involved. The SYSTEM user just won't do network drives. You can try
creating a domain user that has rights equivalent to SYSTEM (read the
openssh_x-x-x.README and in the NTSEC/mkpasswd notes in the cygwin FAQ),
but this could be dangerous.
I don't know about the CYGWIN variable not being set- is it a system
variable, or a user variable? But I don't think it "prevents" SYSTEM
from accessing network drives, that is a known NT limitation.
HTH,
Peter
Noel Yap wrote:
> I'm still having problems with cron jobs accessing
> other machines. I've tried writing directly to
> network drives, rsh'ing to the other machine, and
> making the SYSTEM user part of the Administrator
> group, but nothing I've tried works.
>
> My CYGWIN env var is set to "binmode export ntsec tty"
> but when I do "echo $CYGWIN" from bash, it's not set.
> Could this have something to do with it?
>
> Any help on this matter would be greatly appreciated.
>
> Thanks,
> Noel
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> 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/
>
>
--
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/
- Raw text -