This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: rshd children can't use sockets (they can't get at hostnames)
- To: Mark Keil <Mark dot Keil at cportcorp dot com>
- Subject: Re: rshd children can't use sockets (they can't get at hostnames)
- From: egor duda <deo at logos-m dot ru>
- Date: Fri, 18 May 2001 21:56:49 +0400
- CC: cygwin at cygwin dot com
- Organization: deo
- References: <50A89B19AEAAD411B9D200A0C9FB5699B34A72@craius.cportcorp.com>
- Reply-To: egor duda <cygwin at cygwin dot com>
Hi!
Friday, 18 May, 2001 Mark Keil Mark.Keil@cportcorp.com wrote:
MK> network related commands fail when run as a rshd child process,
MK> but succeed if run from rlogin to the same NT machine.
MK> What is it about the rshd context that causes this behavior?
MK> Is some subsystem not set up by rshd?
probably, missing SYSTEMROOT environment variable. rshd cleans
children environment, and this prevents winsock from initializing
correctly. cygwin has been patched recently to force SYSTEMROOT and
SYSTEMDRIVE for all child processes, and it, hopefully, wil fix your
problem. try latest snapshot or wait for upcoming 1.3.2 release.
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple