https://bugs.freedesktop.org/show_bug.cgi?id=48341
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NOTABUG | Ever Confirmed|0 |1 --- Comment #6 from [email protected] 2012-05-03 06:14:35 PDT --- Starting with the soffice script in a daemon on linux isn't feasible because it doesn't give the starting process any way to kill the real soffice.bin process. On Windows killing the parent process kills soffice.bin, but on linux one ends up with a bunch of zombie soffice.bin processes. If it isn't possible to start soffice.bin directly, please can we have a reliable way to kill the soffice.bin process (a file with the PIDs for both soffice.bin and oosplash would be adequate). Note that this is needed in the case where soffice.bin is no longer responding, so using the API is not an option. Interestingly I've only started being hit by this problem with LibO_3.5.3rc2_Linux_x86-64, on a different virtual machine I am using LibO_3.5.1rc2_Linux_x86-64 and it is working correctly. -- 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
