https://bugs.freedesktop.org/show_bug.cgi?id=49432
Bug #: 49432
Summary: No way to cleanly shutdown LibreOffice when run in a
headless way and accessed solely via the API
Classification: Unclassified
Product: LibreOffice
Version: LibO 3.5.3 release
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: UNCONFIRMED
Severity: blocker
Priority: medium
Component: Libreoffice
AssignedTo: [email protected]
ReportedBy: [email protected]
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.
There is no way to get the PID of soffice.bin (or oosplash) if they are started
by the soffice script.
Furthermore there is no way in java to kill any process except one that is
directly started from java.
The result is that problematic instances of soffice.bin remain alive with no
connection to them.
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.
I have filed this issue as a blocker because it is preventing me from upgrading
to 3.5.3.
There are a number of options for resolving this, but the best for me would be
for there to be a documented way to run soffice.bin directly.
Simpler for LibreOffice would be to simply write the PIDs for any started
process to a known location (within the env).
--
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
