Welcome, Guest
Please Login or Register.    Lost Password?

Display number for Go-Global session?
(1 viewing) (1) Guest
Go to bottomPage: 1
TOPIC: Display number for Go-Global session?
#3478
Display number for Go-Global session? 6 Years, 5 Months ago Karma: 0
OK. Connecting to CDE on a unix server. Able to login - works great.

What I want to do is then log into another server, change the DISPLAY variable, run an x application and get the display back on my go-global cde session.

What do I need to set DISPLAY= ? I understand DISPLAY=ip addr:x.x but what about x.x?
williams
Fresh Boarder
Posts: 1
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#3479
Re:Display number for Go-Global session? 6 Years, 5 Months ago Karma: 2
The short answer is that it automatically scans for the next "available" DISPLAY number and uses that. Normally you'll want to somehow maintain the DISPLAY environment variable when you log into the remote machine; obviously there are lots of ways to do this automatically, and at worst you can manually set it to the value that appears in the GO-Global title bar (if in single window mode) or the Connection/Running Session menu or by running "echo $DISPLAY" from a Terminal.

Don't forget to enable access from the remote host in the GO-Global session.

The long answer is: there are three settings in ${GOGLOBAL_ROOT}/etc/gold.conf that determine how GO-Global picks the DISPLAY number:


  • min_display - the first display number available for allocation (defaults to 1).

  • max_display - the last display number available for allocation (defaults to 2000).

  • use_first_display - determines the allocation method (see below)



If use_first_display is true (the default) then each time GO-Global is starting a new X session, it will begin at min_display and scan for an available DISPLAY value up to max_display. If it does not find one, it will report an error.

If use_first_display is false then each time GO-Global is starting a new X session, it will begin at the most recently started DISPLAY number and scan for an available DISPLAY up to max_display. If it does not find one, it will start over at min_display and scan up to the most recently started DISPLAY number. If it still can't find one, an error is reported. This mode was implemented for special use cases where customers would "accidentally" run jobs against X servers that used to be active but were no longer being used. They wanted to avoid having those jobs (at some later time) come up on what would now be another user's DISPLAY. By avoiding the reuse of the DISPLAY numbers for a period of time, they can minimize the chance that this would happen.

Hope this information is helpful.

Troy
troy
Administrator
Posts: 231
graphgraph
User Offline Click here to see the profile of this user
Gender: Male Birthday: 01/14
Last Edit: 2011/06/02 04:16 By troy.
The administrator has disabled public write access.
 
Go to topPage: 1
Moderators: troy, Andyl