On 2019-06-03 15:48, Hauke Fath wrote:
I have an old script around that will open a file with gnuclient in
an
existing XEmacs instance, or start one up first.
Since I mentioned this...
My script will try to attach to a running gnuserv, and start a new one
if that fails:
if ! gnuclient -batch -eval t >/dev/null 2>&1
then
xemacs -unmapped -eval gnuserv-start &
sleep 1
until gnuclient -batch -eval t >/dev/null 2>&1
do
sleep 1
done
fi
This works as intended, most of the time.
But every now and then, the gnuserve instance so created will not be
responsive, and the until keeps looping. Every new invocation of the
script will leave behind another xemacs process running an unresponsive
gnuserv. Funny enough, starting
% xemacs -unmapped -eval gnuserv-start &
in another xterm will result in an accessible gnuserv...
Usually this problem appears and disappears in the context of seemingly
unrelated system updates and/or xemacs rebuilds.
Can anybody make heads or tails of the above, or provide debugging tips?
Cheerio,
hauke
--
The ASCII Ribbon Campaign Hauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
Respect for open standards Ruf +49-6151-16-21344