/usr/sbin/ipconfig waitall is already part of the default startup
script for wotaskd and JavaMonitor but it didn't work on Snow Leopard
for some reason.
Did some more research and seems like using the Network Reachability
Framework API can be used for this and other launchd Daemons.
Turns out that it was the launchd launch daemon. It was starting
wotaskd and JavaMonitor before setting up the network for the machine
resulting in weird behavior. Adding sleep 15 to the wotaskd and
JavaMonitor init script solved the problem. I'm looking into a better
way of doing
We had a similar problem with Tomcat starting before network was
ready. We solved the problem by putting
/usr/sbin/ipconfig waitall
in the tomcat startup script. This might help here, and be a bit more
reliable than just sleeping for 15 seconds.
Tim
On 03/08/2010, at 9:22 AM, Tusker
I thought that was fixed since 10.5something
On Aug 2, 2010, at 4:22 PM, Tusker wrote:
Turns out that it was the launchd launch daemon. It was starting wotaskd and
JavaMonitor before setting up the network for the machine resulting in weird
behavior. Adding sleep 15 to the wotaskd and
