xvfb set with DISPLAY=localhost:0.0

[Michael O'brien_1]

Hi,

I have a requirement to have xvfb display buffer running with a XVFB_DISPLAY=0 rather than the default XVFB_DISPLAY=5 (/etc/rc.config.d/xvfb)

Unfortunately when I then export DISPLAY=localhost:0.0 and then fire up xclock it errors with can;t open display. It works fine with if I have have the XVFB_DISPLAY=5 and DISPLAY=localhost:5.0

Previously we used the older implemnetation of xvfb and the display was set to DISPLAY=localhost:0.0

Can anyone advise why I have an issue when I set DISPLAY=localhost:0.0

Thanks
Michael

[Steven E. Protter]

Shalom Michael,

You don't want to run xvfb to the same display you would run x windows for system configuration.

More than likely localhost:0.0 is being used by a X windows program monitoring your machine.

My operators in chicago liked to keep gpm up on the systems and that used 0.0. If you try to do x writes to that it will pop up there.

I assume you are using xvfb to provide X services to some product like Oracle reports.; Go with 5 and be happy it works at all. :-)

SEP

[Deepak Kr]

Michael,

What is the issue you face you run xvfb using default XVFB_DISPLAY=5 in /etc/rc.config.d/xvfb

[Michael O'brien_1]

Thanks for your reply's to my question.

I have managed to fix the problem by changing the USE_XHP=0 in the /etc/rc.config.d/xvfb

# Set to "0" to force use of Xvfb instead of Xhp as VFB
# If XHP_VFB_BROKER is n/a, will fallback to "0"

USE_XHP=0

I agreed totally with you SEP that using the default xvfb display 5 would be the best sloution and the customer does infact use display 5 in all of the dev environments but for some historical reason that use display0:0 in production. Getting the customer to change the display settings in an E-Buisness suite environment wasn't really an option.

Without changing the variable USE_XHP=0 xvfb looks for /dev/crt device file as you would expect because using display 0 is used for the physical card.

Thanks again for your input.

Cheers
Michael