Subject: systemroot is it, was RE: rshd children can't use sockets (they c an't get at hostnames)
From: Mark Keil <[email-masked]>
To: egor duda <[email-masked]>
Cc: [email-masked]
Date: Fri, 18 May 2001 14:12:40 -0400

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:[email-masked]]
> Sent: Friday, May 18, 2001 1:57 PM
> To: Mark Keil
> Cc: [email-masked]
> Subject: Re: rshd children can't use sockets (they can't get at
> hostnames)
> 
> 
> Hi!
> 
> Friday, 18 May, 2001 Mark Keil [email-masked] 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:[email-masked] ICQ 5165414 FidoNet 
> 2:5020/496.19
> 
> 

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple