Hi Guys, I have a problem that I would like to put past some of you. The generic details are as follows - I have a program that I need to connect to an instance of Open Office 2.1 running in headless mode, and to do this, I have Xvfb running a display for it to connect to.
The above scenario works fine on one installed box of Solaris 10, and everything runs fine, when launching the Open Office process, it successfully connects to the Xvfb screen and creates a listening socket on port 2002 - to which my program can successfully connect. Now the problem occurs when I wan to run the same Xvfb + Open Office combination on another box (production machine - left in fairly virgin state until we have all the final tweaks ironed out). What happens is that the Xvfb display process launches fine, the Open Office process appears to launch and connect to the Xvfb screen just fine also, *except* for one noteable difference, the listening socket on port 2002 never gets created. Below [1] is the script that I use to launch the whole thing. I've trailed through Open Office forums ad nauseum to try and find an answer - to no avail. What I would like to know is what/where/how can I check for something that might preventing this process from opening a socket on port 2002? I've had no problems with either debian (ubuntu) and RHEL 4 in running variations of this script. Any pointers would be greatly appreciated, Regards, Richard [1] Script used to invoke Xvfb and soffice running in headless mode: #!/bin/sh PATH=$PATH:/usr/openwin/bin:/opt/csw/OpenOffice.org/program/;export PATH Xvfb :5 -dev vfb screen 0 800x600x16 -pn & #Storing pid for shutdown script echo $! > xvfb.pid DISPLAY=:5;export DISPLAY echo "Screen is now: $DISPLAY" echo "Launching Open Office in headless mode" soffice -display :5 -accept="socket,host=localhost,port=2002;urp;" & #Storing pid for shutdown script echo $! > soffice.pid _______________________________________________ opensolaris-discuss mailing list [email protected]
