Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <50A89B19AEAAD411B9D200A0C9FB5699B34A7A@craius.cportcorp.com> From: Mark Keil To: egor duda Cc: cygwin AT cygwin DOT com Subject: systemroot is it, was RE: rshd children can't use sockets (they c an't get at hostnames) Date: Fri, 18 May 2001 14:12:40 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" ahhh, that is exactly it, thankyou! $ rsh NTBOX "export SYSTEMROOT=C:\WINNT; nslookup cygwin.com" Non-authoritative answer: Server: zzz.yyy.com Address: 192.168.xxx.xx Name: cygwin.com Address: 205.180.83.71 -Mark > -----Original Message----- > From: egor duda [mailto:deo AT logos-m DOT ru] > Sent: Friday, May 18, 2001 1:57 PM > To: Mark Keil > Cc: cygwin AT cygwin DOT com > Subject: Re: rshd children can't use sockets (they can't get at > hostnames) > > > Hi! > > Friday, 18 May, 2001 Mark Keil Mark DOT Keil AT cportcorp DOT 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 AT logos-m DOT ru ICQ 5165414 FidoNet > 2:5020/496.19 > > -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple