From: Alan W. <arw...@wo...> - 2005-06-14 23:59:11
|
>> 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? put a sleep in the startup code for a few seconds.. Alan |
From: Matthew W. <mat...@us...> - 2005-06-20 19:12:24
|
Chris Barrett wrote: >> I had thought of that but the problem is that it doesn't guarantee success >> and it would have to be a long enough delay to ensure that it worked on all >> systems. >> >> I'll do it that way if need be but I'm hoping for something that you can be >> sure will work every time, or at least very close to every time. >> >> I know that other, better, solutions have been posted. But I thought that the following might be useful in general cases when you need to wait for certain things to happen in scripts. How about putting in a while loop that uses netstat to wait for the listen port to become active? Something like this: waittime=10 i=0 while true; do if [ $i -ge $waittime ]; then break fi netstat -ln | grep tcp | grep LISTEN | grep -q 3639 if [ $? -eq 0 ]; then break fi sleep 1 (( i += 1 )) done if [ $i -eq $waittime ]; then # netstat never detected the port open # after waiting for at least waittime seconds # handle the error fi |
From: Chris B. <ch...@ba...> - 2005-06-15 00:11:03
|
I had thought of that but the problem is that it doesn't guarantee success and it would have to be a long enough delay to ensure that it worked on all systems. I'll do it that way if need be but I'm hoping for something that you can be sure will work every time, or at least very close to every time. > -----Original Message----- > From: mis...@li... [mailto:misterhouse- > use...@li...] On Behalf Of Alan Womack > Sent: Wednesday, 15 June 2005 9:59 AM > To: Alan Womack > Subject: re: [mh] xap-festival steals 3639 from MH > > >> 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? > > put a sleep in the startup code for a few seconds.. > > Alan |