On 28/08/2019 12:43, Jerry Geis wrote:
Thanks - I even rm -rf that /tmp file, checked again with ps ax | grep
office and nothing, started up again and it says the same thing.
I even rebooted and that process is not running.
my command line instance just exits like before.
So what's the exact c
Thanks - I even rm -rf that /tmp file, checked again with ps ax | grep
office and nothing, started up again and it says the same thing.
I even rebooted and that process is not running.
my command line instance just exits like before.
Is there a way to say Skip single instance or something like tha
On 28/08/2019 12:20, Jerry Geis wrote:
There's apparently another instance of soffice.bin already running (for
the same UserInstallation), so this one just passes its cmd line args
(none in this case) to the other instance and exits successfully.
Thank you - Where/how does it get this? I ha
>There's apparently another instance of soffice.bin already running (for
>the same UserInstallation), so this one just passes its cmd line args
>(none in this case) to the other instance and exits successfully.
Thank you - Where/how does it get this? I have --nolock on the command line,
the fi
On 28/08/2019 03:13, Jerry Geis wrote:
[pid 3559] connect(4, {sa_family=AF_LOCAL,
sun_path="/tmp/OSL_PIPE_0_SingleOfficeIPC_53bc4297d6d012e1a744f3977d159334"},
110) = 0
There's apparently another instance of soffice.bin already running (for
the same UserInstallation), so this one just passes
here is the strace of soffice.bin -
I have loaded 6.3.0.4 on CentOS 7 on two machines - first machine it worked
- this machine
its not running - and just exists...
Sometimes I see Application error - sometimes not.
What is it not happy about, how can I get it running ???
Thanks
Jerry
[pid 3559]
