On Jun 26, 2008, at 10:49 AM, Miguel Arroz wrote:
My guess is that it has nothing to do to the power outage, but with
and "old" problem. Check this mail from Cliff from some months ago:
I thought my solution was definitive! :-) See the thread titled
"Security
Update 006-2007". Just edit
/System/Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd and
add a
"sleep 5" (no quotes) up near the top. Haven't heard one complaint
about
that solution yet.
WO 5.4 implemented a better fix that should work under Tiger Server/
WO 5.3 as well. Insert the following
#
# Verify network services are intialized before starting
#
echo Checking network services....
if [ "${PLATFORM_TYPE}" = "Darwin" ]
then
/usr/sbin/ipconfig waitall
fi
just prior to
#
# Launch the application.
#
in the wotaskd shell script in wotaskd.woa and wotaskd.woa/Contents/
MacOS. For good measure, do the same in the JavaMonitor shell script
in JavaMonitor.woa and JavaMonitor.woa/Contents/MacOS.
The "sleep 5" workaround may be insufficient in some situations
whereas the WO 5.4 fix should work in all situations (assuming Mac OS
X Server deployment).
Aloha,
Art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
