To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=93031
                 Issue #|93031
                 Summary|Setting UserInstallation prevents binding the socket
               Component|Word processor
                 Version|OOo 2.4.1
                Platform|Other
                     URL|
              OS/Version|Linux
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|configuration
             Assigned to|mru
             Reported by|wdonne





------- Additional comments from [EMAIL PROTECTED] Fri Aug 22 14:46:56 +0000 
2008 -------
I have started soffice with the following command-line:

> soffice -headless -norestore "-accept=socket,host=0,port=22222;urp;"
-env:UserInstallation=file:///tmp/tt

/tmp/tt is an existing directory.

The process starts and waits, but a client gets "Connection refused", which
leads me to think the socket isn't bound in soffice. When I leave out the
UserInstallation option the client can connect.

With the UserInstallation directory set to /tmp/tt I see the "user" subdirectory
is created with everything in it, but there is no ".lock" file, which would be
the case with the default user directory.

PS: I see no point in locking when soffice is in headless mode.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to