On Thu, 2002-08-08 at 19:05, Harry Felder wrote:
I do a
rsh foo DISPLAY=bar:0.0 /usr/local/bin/xemacs-new -q
from a console window on bar to the remote system foo.
(xemacs 21.4.8 is doing business as xemacs-new.)
Then do an xkill from any system on the XEmacs window, which
generates on bar the output:
xemacs: Fatal I/O Error 32 (Broken pipe) on display connection "bar:0.0"
after 2659 requests (2659 known processed) with 0 events remaining.
And the XEmacs process on foo attempts to use 100% of the CPU.
ISTR I've seen this too, when ssh'ing (X11-forwarded) to a Linux box
running 21.4.8 from a Windows box, using Exceed. If the ssh connection
dies, xemacs will take 100% CPU in the Linux box.
--
\/ille Skyttä
ville.skytta at
xemacs.org