Has someone been messing with the networking code?  I tried starting
up XEmacs on my laptop, and it just hung until I started PPP when
Wham! there it was in my face.  The "change DISPLAY" trick may also
have worked.  I haven't figured out how to investigate this properly
(my net config on that box is an unholy mess, it needs to cope with
three different fixed IP addresses depending on where it gets plugged
in, and with dynamically assigned PPP).
XEmacs CVS updated to 2/26 21:00 JST, updated again 2/28 22:00 JST.
Debian GNU/Linux "woody".
Could these be related?
>>>> "kkm" == Kirill 'Big K' Katsnelson
<kkm(a)dtmx.com> writes: 
    kkm> strace also helped, it was stuck on DNS resolution,
    kkm> repeatedly bombing DNS servers with a query.  When I changed
    kkm> DISPLAY from :0.0 to 127.1:0.0, XEmacs started just fine.
>>>> "Andre" == Andre Srinivasan
<andre(a)slamdunknetworks.com> writes: 
    Andre> Efs/ftp was working with 21.2.28, under Cygwin using
    Andre> ftp.exe from inetutils.  When I upgraded to 21.2.29,
    Andre> efs/ftp blocks when trying to open a connection.  What's
    Andre> odd is that all other subprocess kinds of stuff works
    Andre> (compilation, vc, etc).
-- 
University of Tsukuba                Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences       Tel/fax: +81 (298) 53-5091
_________________  _________________  _________________  _________________
What are those straight lines for?  "XEmacs rules."