To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102064 Issue #|102064 Summary|soffice -accept=socket should exit with error if port |busy Component|framework Version|OOo 3.1 Platform|Unknown URL| OS/Version|Linux Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|tm Reported by|mnasato
------- Additional comments from mnas...@openoffice.org Tue May 19 14:02:02 +0000 2009 ------- OOo can be made to listen on a given port for use with remote UNO by starting it with the -accept switch, e.g.: $ soffice "-accept=socket,host=0,port=2002;urp;" If there already is another process listening on the same port (e.g. a web server), I would expect the above command to exit with a code other than 0. Instead it starts anyway apparently without errors, but of course it won't be listening on the port that was already busy. So an external application starting OOo won't be notified of any errors, but won't be able to connect to it either. Additionally, OOo seems to consume 100% of one CPU. (This may or may not be related to issue 94471.) --------------------------------------------------------------------- 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: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
