https://bugs.freedesktop.org/show_bug.cgi?id=49432
Stephan Bergmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Stephan Bergmann <[email protected]> 2012-05-04 00:55:58 PDT --- (In reply to comment #0) > With LibO_3.5.1rc2_Linux_x86-64 I was able to start soffice.bin directly and > kill it after something bad had happened. > With LibO_3.5.3rc2_Linux_x86-64 I am unable to start soffice.bin directly (by > design, according to bug 48341), which means I have to start it via the > soffice > script. Generally, it has never been supported to start anything but the outermost soffice directly. If starting anything else appeared to work, that always was by coincidence. And nothing changed in this regard between LO 3.5.1 and 3.5.3; in both versions, soffice.bin can exit early with code 81, expecting the wrapping process to restart it. This has been so at least since LO 3.4. > For LibreOffice to be useful in a headless, API only, daemon environment it > needs to be possible to start multiple instances (concurrently) and to kill > them reliably after problems occur. Killing reliably is, by definition, nothing LO itself can cooperate in doing "after problems [in LO] occur" (as LO can be in an undefined state then). (On Unix, you could probably experiment with process groups to reliably send SIGKILL to all processes in a group.) I understand the problem you are facing, but I'm not aware of a good solution for it, short of making LO crash less often. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
