start OpenOffice in MAC OS 10.6

[Владимир Мурзабаев]

Can`t setup autostart OpenOffice.

/Applications/OpenOffice.org.app/Contents/MacOS/soffice.bin -headless -nofirststartwizard -accept="socket,hoslocalhost,port=8100;urp;StarOffice.Service"

work only if i run manual in screen. 

[seba....@gmail.com]

it is not called hoslocalhost but localhost.

You might simply integrate this call into the red5.sh instead of the
system settings.

Sebastian

2011/10/27 Владимир Мурзабаев <murz...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups
> "OpenMeetings User" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/openmeetings-user/-/eD8FtFMbA6kJ.
> To post to this group, send email to openmeet...@googlegroups.com.
> To unsubscribe from this group, send email to
> openmeetings-u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/openmeetings-user?hl=en.
>

--
Sebastian Wagner
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba....@gmail.com

[Владимир Мурзабаев]

I try:

# start Red5

echo "Starting Red5"

exec "$JAVA" "$JYTHON" -Dred5.root="${RED5_HOME}" $JAVA_OPTS -cp "${RED5_CLASSPATH}" "$RED5_MAINCLASS" $RED5_OPTS

exec /Applications/OpenOffice.org.app/Contents/MacOS/soffice.bin -headless -nofirststartwizard -accept="socket,host=localhost,port=8100;urp;StarOffice.Service"

OM starting, OOfice don`t start, 8100 port not listen.

[solomax]

Its not very good idea to put 2 exec one by one
you even need to end first one by "&" sign
or run it as a separate command
please try to run
exec /Applications/OpenOffice.org.app/Contents/MacOS/soffice.bin -
headless -nofirststartwizard -
accept="socket,host=localhost,port=8100;urp;StarOffice.Service"
in the separate Terminal first
then ensure it is running
ps -ef|grep office

[Владимир Мурзабаев]

# start Red5
echo "Starting Red5"

exec /Applications/OpenOffice.org.app/Contents/MacOS/soffice.bin -
headless -nofirststartwizard -

accept="socket,host=localhost,port=8100;urp;StarOffice.Service" &

exec "$JAVA" "$JYTHON" -Dred5.root="${RED5_HOME}" $JAVA_OPTS -cp "$
{RED5_CLASSPATH}" "$RED5_MAINCLASS" $RED5_OPTS

ps -ef|grep office
0 8068 8065 0 0:00.17 ?? 0:00.64 /Applications/
OpenOffice.org.app/Contents/MacOS/soffice.bin -headless -

nofirststartwizard -
accept=socket,host=localhost,port=8100;urp;StarOffice.Service

soffice run, but not open 8100 port
# netstat -an | grep 8100
ffffff801f387f80 stream 0 0 0
ffffff801f388100 0 0 /var/run/
caldavd.sock
ffffff801f388100 stream 0 0 0
ffffff801f387f80 0 0

[Владимир Мурзабаев]

What to do?
logs:
Oct 28 14:33:07 macserver com.openmeetings.start[9059]: Running on
Darwin
Oct 28 14:33:07 macserver com.openmeetings.start[9059]: Starting Red5
Oct 28 14:33:07 macserver soffice.bin[9062]: 3891612:
(connectAndCheck) Untrusted apps are not allowed to connect to or
launch Window Server before login.
Oct 28 14:33:07 macserver soffice.bin[9062]: kCGErrorFailure: Set a
breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Oct 28 14:33:07 macserver com.openmeetings.start[9059]: Fri Oct 28
14:33:07 macserver.private soffice.bin[9062] <Warning>: 3891612:
(connectAndCheck) Untrusted apps are not allowed to connect to or
launch Window Server before login.
Oct 28 14:33:07 macserver com.openmeetings.start[9059]: Fri Oct 28
14:33:07 macserver.private soffice.bin[9062] <Error>:
kCGErrorFailure:
Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are
logged.
Oct 28 14:33:07 macserver /Applications/OpenOffice.org.app/Contents/
MacOS/soffice.bin[9062]: _RegisterApplication(), FAILED TO establish
the default connection to the WindowServer, _CGSDefaultConnection()
is
NULL.
Oct 28 14:33:07 macserver com.openmeetings.start[9059]:
_RegisterApplication(), FAILED TO establish the default connection to
the WindowServer, _CGSDefaultConnection() is NULL.
Oct 28 14:33:08 macserver com.openmeetings.start[9059]: Red5 root:

http://developer.apple.com/library/mac/#technotes/tn2083/_index.html
Pre-Login Trust Issues

If, in Mac OS X 10.5 and later, you see a message like that shown in
Listing 9 you might mistakenly think that the solution is to get the
system to 'trust' your application, perhaps via code signing.

Listing 9 Pre-Login Trust Message

Untrusted apps are not allowed to connect to or launch Window Server
before login.

However, this isn't the case (r. 5544764) . This message is really
telling you is that you're trying to connect to the window server from
the wrong context. You see this message if you try to connect to the
global window server service from outside of the pre-login context
before the user has logged in; typically this means that you're trying
to use the window server from a daemon.

You should not attempt to fix this by convincing the window server to
trust your program; doing so will just cause other problems further
down the road. For example, if you do successfully connect to the
window server from your daemon, you still have to deal with window
server lifecycle issues described previously.

Instead, you should fix this problem by changing your code to run in
the correct context. If you need to connect to the window server in a
pre-login context, create a pre-login launchd agent. For an example of
this, see Sample Code 'PreLoginAgents'.

[Alexei Fedotov]

> Instead, you should fix this problem by changing your code to run in the correct context.

You are welcome to send the patch :-)

--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://dataved.ru/
+7 916 562 8095

2011/10/28 Владимир Мурзабаев <murz...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups "OpenMeetings User" group.