Pierre -- Pierre Frisch [EMAIL PROTECTED]
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 (Webobjects- [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]
