[AAAAARGGHHHH... Yet another I started XEmacs from my WM problem, it
must be the heat wave.]
giacomo boffi <boffi(a)rachele.stru.polimi.it> writes:
1. let my WM (gwm) start xemacs like this
xemacs -f gnuserv-start
2. exit xemacs
3. observe a gnuserv process that eats up to 95% of cpu
Please attach 'strace' to gnuserv to see what it is doing just before
and after XEmacs is exited.
P.S. What happends when you just do 'xemacs' from your WM and then M-x
gnuserv-start.
P.P.S. What happens when you use
'xemacs -f gnuserv-start <somefile >someotherfile 2>&1'
And what happens if you use this script (possibly from an xterm)
#!/usr/bin/perl
close STDOUT;
close STDIN;
close STDERR;
exec "xemacs","-f","gnuserv-start"