Tip:
Highlight text to annotate it
X
Using the RM Converter Application Configuration and Troubleshooting Guide,
review the system requirements for the virtual frame buffer. For Linux, you will require the Xvfb file and GTK2.
Using the RM package query you can find out which packages have been installed on the system.
You will also need to export a display variable to make sure that the frame buffer understands which display you are working with.
To support the virtual frame buffer startup process, create a test Xvfb source file.
In this source file have DISPLAY exported on localhost screen three.
You must talk to your system administrator to find out if screen three is available. It is possible that it is not.
You could choose screen three, four or five or even screen two if it is available to you.
Then setup a command to startup a frame buffer and an output log file to this command. Then there is a test to find out if
the Xvfb process is up and running already when we log onto the system.
To launch this source file, type source tstXvfb
or ". tstXvfb". Both commands are equal to the source command.
Once you have sourced the tstXvfb, it should have tested if the Xvfb process is up and running. If it not, a new process will be invoked.
You can review the log file that is created by the script and validate that the process ID is up and running.
To kill the Xvfb process you need to use the kill command.
Kill the process on the port that it was started. This is because you will load this file into a bash
process so that each time the root user logs in it will run the Xvfb process. This is optional.
Talk to your system administrator to find out which process is supported for starting the Xvfb process.
This is just an example.
In this case, update the bash profile with your source command for tstXvfb.
Now to prove that your bash process is working correctly and as expected you
can open a new terminal and login as the root user. This should effectively call the bash profile
and source the file into the environment for that root user at logon.
As you have a condition to test if our Xvfb process is up and running in the system, this will launch an Xvfb process if
and only if there is no process running. Otherwise it will ignore the launch command.
As we can see, when you logged in the source command actually did load the frame buffer.
If you review the log file for the source script that you created,
you can see that the frame buffer has actually been started on the same Process ID.