On Aug 11, 2008, at 4:02 PM, Art Isbell wrote:
On Aug 11, 2008, at 12:21 PM, Pierce T. Wetter III wrote:
1. Put a "sleep 30" in the script that launches wotaskd.
wotaskd can launch before the network is up, and latch onto a
useless ip address like, say 127.0.0.1, which makes its hard for
anyone to talk to it. It was better before launchd, because with
Startup items it had "Network" in there, so it wouldn't launch
until after the Network was up. Now that its brought up by launchd,
it launches too soon.
Adding a "sleep" statement to the wotaskd scripts in wotaskd.woa
and wotaskd.woa/Contents/MacOS and to the JavaMonitor scripts in
JavaMonitor.woa and JavaMonitor.woa/Contents/MacOS was the initial
workaround to this problem when faster deployment servers began
being used. But if the sleep period is insufficient, the problem
persists.
The much better solution was added to these scripts by Apple with
WO 5.4. Insert the following into the same scripts near the end of
the script:
#
# Verify network services are intialized before starting
#
echo Checking network services....
if [ "${PLATFORM_TYPE}" = "Darwin" ]
then
/usr/sbin/ipconfig waitall
fi
just before
Cool, though what I said about DHCP still applies.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
