Zak,Where did you get the launchd script from? They are not included in MacOS 10.5 client. If you copied them from server this why you are seeing that behavior. On server the default settings are different. On MacOSX 10.5 client Apple install the deployment version of WO the main differences are the default settings and the launch scripts.
You can fix the problem by adding the WOAutoOpenInBrowser false in the launch parameters of the launchd script.
Of course you could simplify your life and deploy on MacOSX server… Pierre -- Pierre Frisch [EMAIL PROTECTED] On Jan 30, 2008, at 13:09, Zak Burke wrote:
On Jan 30, 2008, at 3:03 PM, Mr. Pierre Frisch wrote:For security reason it is highly discouraged to run monitor as root. _appserver has the bare minimum privileges to run and certainly cannot launch an application in the user space. This is the correct behavior. If you are running on MacOSX server you will notice that the defaults for WO application are different and WOAutoOpenInBrowser is not set.Right; I understand that running as root is wrong wrong wrong. I did it just for testing. But it seems odd to me that the default behavior is:1. run as a user without app-launching permissions 2. auto-launch an app (1) is correct but (2) should be fixed. Bug filed: Bug ID# 5715638. zak.On Jan 30, 2008, at 10:11, Zak Burke wrote:I am having a collection of problems running WO applications under Mac OS 10.5, WO 5.4, Apache 2.2. In trying to debug those problems, I stumbled on this one, which isn't really a problem, but it's still kind of a head scratcher. Here's the situation:When womonitor is set to run as _appserver, it generates a Safari crash report in syslog. This appears to be because JavaMonitor's Properties file contains "WOAutoOpenInBrowser=true" and _appserver doesn't have shell or console access or whatever it is you need to launch Safari. When I switch womonitor to run under my own account, Safari happily launches and displays the JavaMonitor front page, so this bears out the "_appserver doesn't have permission to launch console apps" idea. That led me to try running womonitor as root. That generated no crash log, but also didn't launch Safari.So I have two questions:1. What's going on when womonitor runs as root? How is it possible that Safari fails to launch, but without a crash report?2. Should the default setting in JavaMonitor's Properties file for WOAutoOpenInBrowser be false since the recommended settings cause a crash?zak. _______________________________________________ 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/pierre%40apple.com This email sent to [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
