Hi :)
In Debain family maybe "pkill" might be better to kill a named process
rather than by it's id? Wouldn't a "kill" (or "pkill") command also mean
the next time you open LibreOffice it'll try to recover a file?
I'm not sure about any of this so i'm just wondering. I tend to stay as
far away from the command-line as possible but occasionally find myself
doing odd things there.
Regards from
Tom :)
On 31 October 2014 14:05, Paul D. Mirowsky <p_mirowsky@bentaxna.com> wrote:
You might have to run a logout script from some type of ".rc" file.
This is not the actual command and is not the best way to do it. It should
be possible.
The script will have a
kill -9 soffice.bin
and will need code to find it with 'ps'.
See https://unix.stackexchange.com/questions/2745/how-to-run-
a-script-during-gnome-log-out as an example from Gnome.
Hope this helps.
On 10/31/2014 7:20 AM, rmg wrote:
I'm migrating a bunch of spreadsheets from Debian Lenny/Openoffice to
Debian Wheezy/Libreoffice 3.5.x. This is a dedicated setup used by many
once-a-year users (who aren't chosen for their familiarity with computers)
and, for instance, boots straight into a front end when switched on and
shuts down when you close the front end. All driven by a startup script
which launches the front end and waits for it to close.
The front end is fundamentally some buttons to launch working sheets and
unchanging except that today's date is filled in when it starts, or the
user can enter a different date. Mass of macros to handle it all.
Closing the front end is by doc.close()ing in a Goodbye macro but this
leaves an soffice.bin process running and you get a 'Program is still
running' dialogue box when the machine shuts down; it goes away after a bit
but it will alarm the user. I can get rid of that by putting
'stardesktop.terminate' (is 'xdesktop.terminate' preferrred?) in the
shutdown macro but then when it next starts it wants to Recover the front
end; that's a big no-no.
Under Lenny/Openoffice there isn't this problem, when you've doc.close()d
it shuts down happily and when it's next switched on loads the front end
without complaint. I've tried doc.setmodified(FALSE) but no joy. I suppose
I could get the shutdown macro to save it and the startup script to then
delete that and copy the master back but that's pretty horrible. Is there a
sensible way to fix this?
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-
unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be
deleted
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.