Hello.
Using LibreOffice 3.4/3.5.
I want to run LibreOffice in--headlessmode for
converting files from .doc to .txt, and want to try outboththe socket and pipe methods.
However, what is not clear to me is this...
1) With thesocketmethod: If I specify an
arbitrary port (instead of the default 8100) in the--acceptargument, how does the the
connecting client (a shell script) know
about this port. In other words, where/how do I specify the port
in the connecting client shell script?
2) With thepipemethod: Do I have to create
the pipe myself (usingmkfifo)beforepassing its name to the--acceptargument, or will
LibreOffice automatically create the pipe for me? Further, how do
I tell the connecting client (again, a shell script) about the
name of this pipe?
Would greatly appreciate if you could give an example invocation
each for the listening and connecting sides, for both the socket
and pipe methods. I have searched the Net far and wide but haven't
found any relevant information.
Many thanks in advance,
/HS
--
For unsubscribe instructions e-mail to: users+help@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
- [libreoffice-users] Headless mode examples for socket and pipe methods. · Harry Simons
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.