To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=93731
------- Additional comments from [EMAIL PROTECTED] Fri Sep 19 11:26:28 +0000 2008 ------- @ericb: That will result in the same effect as when soffice forks itself (and is enteredf in the info.plist) -> Two dock icons on Tiger after restart on crash. I've already tested all combinations of a loder application starting itself or another renamed copy of itself. Also played around with softlinks. All solutions had at side effect at least on one of the two platforms. And a subpackage would have many side effect on OOo packaging process and bootstrapping mechanism. So I feel only two solutions are left: 1. Let soffice (entered in the plist.info) fork itself directly from the signal handler after a crash (might be dangerous depending on which thread crashed) 2. Implement a watch dog that is initial started by soffice and restarts soffice after it detected a crash of soffice. That should definitely work without side effects. Don't know wether it's worth all that effort. I've already played around and tested with it the last 3 days. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
