Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Fri, 18 May 2001 21:56:49 +0400 From: egor duda X-Mailer: The Bat! (v1.45) Personal Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <142189006757.20010518215649@logos-m.ru> To: Mark Keil CC: cygwin@cygwin.com Subject: Re: rshd children can't use sockets (they can't get at hostnames) In-reply-To: <50A89B19AEAAD411B9D200A0C9FB5699B34A72@craius.cportcorp.com> References: <50A89B19AEAAD411B9D200A0C9FB5699B34A72@craius.cportcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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