It runs quickly when everything is up, I don't see a reason to not include it in all the scripts.
Chuck
On 2012-03-02, at 2:23 AM, Pascal Robert wrote:
> It's woproject that will need to be changed since it's woproject job to
> create the launch scripts. So we have to decide if any applications build by
> woproject should have the ipconfig call or it's only for wotaskd and Monitor.
> I think it should be for all applications, because if someone is launching a
> WO app without wotaskd at startup (for example, a product build and sold as a
> .woa), having the call would be useful.
>
>> I was just diffing the application launch scripts for a default
>> wotaskd/javamonitor that I had lying around (not exactly sure which version
>> - probably from 5.3.x) and the Wonder versions - i.e., wotaskd.woa/wotaskd
>> and JavaMonitor.woa/JavaMonitor (not the launchd code).
>>
>> In both cases the stock versions include the following code right before the
>> application is launched - and which is not present in the Wonder versions of
>> the apps (or in my own built apps):
>>
>> # Verify network services are intialized before starting
>> #
>> echo Checking network services....
>> if [ "${PLATFORM_TYPE}" = "Darwin" ]
>> then
>> /usr/sbin/ipconfig waitall
>> fi
>> #
>>
>> It seems that Apple recognized this problem, and took steps to customize
>> each of these 'likely to be launched boot time' applications' boot scripts
>> to deal with it.
>>
>> Is there a way to build the Wonder versions to include modified launch
>> scripts by default? Alternatively, I think you could go with my earlier idea
>> of a dedicated launchd task to wait for the interfaces at that point, and
>> then bring up wotaskd, Monitor and Apache once the network is ready.
>>
>> Simon
>>
>>
>>
>>
>> On Mar 1, 2012, at 1:21 PM, <gsbr...@umich.edu>
>> <gsbr...@umich.edu> wrote:
>>
>>>
>>> I recall modifying the app.woa/app startup script at the end.
>>>
>>> Basically, wotaskd should start first (it will start your app), then after
>>> it is running javamonitor should start. The tail end of my
>>> wotaskd.woa/wotaskd is like:
>>>
>>> #
>>> # Launch the application.
>>> #
>>> # gsb 6/9/2010
>>> # wait untill things boot all the way up
>>> /usr/sbin/ipconfig waitall
>>> #extra time for db
>>> /bin/sleep 100
>>>
>>> #
>>> # Launch the application.
>>> #
>>> echo gb fixed? Launching ${SCRIPT_NAME}.woa ...
>>> echo Launching ${SCRIPT_NAME}.woa ...
>>>
>>> echo ${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar
>>> com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
>>> eval exec ${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath
>>> WOBootstrap.jar com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
>>>
>>>
>>> And for my JavaMonitor.woa/JavaMonitor:
>>>
>>> # gsb 6/9/2010
>>> # wait untill things boot all the way up
>>> /usr/sbin/ipconfig waitall
>>> #extra time for db
>>> /bin/sleep 240
>>>
>>> #
>>> # Launch the application.
>>> #
>>> echo gb fixed? Launching ${SCRIPT_NAME}.woa ...
>>>
>>> #
>>> # Launch the application.
>>> #
>>> echo Launching ${SCRIPT_NAME}.woa ...
>>>
>>> echo ${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath WOBootstrap.jar
>>> com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
>>> eval exec ${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath
>>> WOBootstrap.jar com.webobjects._bootstrap.WOBootstrap ${COMMAND_LINE_ARGS}
>>>
>>>
>>> So I had javamonitor trying to restart wotaskd which was waiting for things
>>> to happen. This did not allow proper startup. With the wait and extra time
>>> for javamonitor reboots work properly.
>>>
>>> I think the apple wo 5.4.3 startups had some waiting; this is the Wonder
>>> versions I had to modify.
>>>
>>> A wait maybe should be added to the Wonder wotaskd and JavaMonitor startup
>>> scripts.
>>>
>>> I could be wrong, of course.
>>>
>>> Greg Brown
>>> gsbr...@umich.edu
>>>
>>>
>>>
>>> --
>>> gsbr...@umich.edu
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/sjoliver%40memphis.edu
>>>
>>> This email sent to sjoli...@memphis.edu
>>
>> --
>>
>> Simon J. Oliver
>> MA (Cantab.)
>> CISSP-ISSAP, ISSMP, GWAPT, OSWP
>>
>> Information, Architecture & Data Security Consultant
>> Applied Information Technology Center/SBBER
>> University of Memphis, TN
>>
>> Phone: 901 313 4485
>> Skype: SJO0923
>> AIM/Yahoo: simonjoliver
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/probert%40macti.ca
>>
>> This email sent to prob...@macti.ca
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net
>
> This email sent to ch...@global-village.net
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their overall
knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/gvc/practical_webobjects
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
