Priest of the Order of the Butterfly
Posts: 874 from 2007/4/9
From: Kingston upon ...
Quote:jPV wrote:
Quote:
boot_wb wrote:
That shd be interval 30 rather than loop 30 then. (Loop 1 is used as a single iteration test in network-startup to test for bsdsocket.library).
Hmm? If you use interval 30, it waits the whole 30 seconds even if the port appears sooner. I don't think that's the wanted behaviour usually. At least I've meant that the command will exit if the network is up after 5 secs and it shouldn't still be waiting for extra 25 secs in that case. But it will wait up to 30 secs if the port doesn't seem to appear sooner.
If you have loop 30 (and the default 1 secs interval) then it checks for the port each second and repeats that 30 times or until the port appears. If you have interval 30, then it only checks for the port after 30 secs if it wasn't initially found.
The default values for WaitForPort are INTERVAL=1 and LOOP=10.
Maybe I should have written "waits for max 30 seconds" in my previous post to be more exact :)
Aha! I'd misunderstood. :)
www.hullchimneyservices.co.uk
UI: Powerbook 5,6 (1.67GHz, 128MB VRam): OS3.1, OSX 10.5.8
HTPC: Mac Mini G4 (1,5GHz, 64MB VRam): OS3.1 (ZVNC)
Audiophile: Efika 5200b (SB Audigy): OS3.1 (VNC + Virtual Monitor)
Windows free since 2011!
