[mh] xap-festival steals 3639 from MH

[Chris B. <ch...@ba...>]

I've noticed that xap-festival is able to bind to port 3639 before mh can
when my MH box is rebooted and then mh complains that 3639 has been taken
and xap doesn't work.

The xap-festival init.d script is started after the one for mh but because
it's so much smaller it is able to grab the port before mh gets the chance
to run the xAP initialisation code during start-up.

At the moment, my fix is to manually stop xap-festival, restart mh and then
start up xap-festival.

To me the obvious fix would to be to modify xap-festival so that rather than
it trying to bind to the first available port in the range of 3639-3739 it
skips 3639 and tries for 3640-3739.  Does anyone know if this is acceptable
under the xAP specification?  If not, are there any other ideas?

BTW I'm assuming that this issue isn't unique to xap-festival and could
occur with any xap client that runs on the same machine as a xap hub.

Cheers,
Chris