The new application startup script fails if the environment variable
HOME is not set. This is a problem since wotaskd is started by
launchd, it has no HOME variable in its environment. Therefore any
apps launched by wotaskd also do not have a HOME environment variable.
As a result, they fail to launch.
I have worked around this problem by adding a HOME environment
variable in the wotaskd launchd plist: /System/Library/LaunchDaemons/
com.apple.wotaskd.plist
For example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd
">
<plist version="1.0">
<dict>
<key>Disabled</key>
<false/>
<key>EnvironmentVariables</key>
<dict>
<key>HOME</key>
<string>/var/appserver</string>
</dict>
<key>GroupName</key>
<string>appserverusr</string>
<key>Label</key>
<string>com.webobjects.wotaskd</string>
<key>OnDemand</key>
<false/>
<key>Program</key>
<string>/System/Library/WebObjects/JavaApplications/
wotaskd.woa/wotaskd</string>
<key>ProgramArguments</key>
<array>
<string>wotaskd</string>
<string>-WOPort</string>
<string>1085</string>
</array>
<key>ServiceIPC</key>
<false/>
<key>UserName</key>
<string>appserver</string>
</dict>
</plist>
This works, but I can't say that I am thrilled with this "solution."
The old app launcher didn't care about HOME, so I wonder if the new
one really needs to.
Wade
This archive was generated by hypermail 2.0.0 : Thu Sep 11 2008 - 17:59:49 EDT