HP Visualize J5000 hp workstations - hp-ux 10.20 graphics administration guide - Page 128

Display Names, Korn Shell

Get HP Visualize J5000 - Workstation PDF manuals and user guides View all HP Visualize J5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 128 highlights

Display Names From the user's perspective, every X server has a display name of the form: hostname:displaynumber.screennumber This information is used by the application to determine how it should connect to the server and which screen it should use by default (on displays with multiple monitors): hostname The hostname specifies the name of the machine to which the display is physically connected. If the hostname is not given, the most efficient way of communicating to a server on the same machine will be used. displaynumber The phrase "display" is usually used to refer to the collection of monitors that share a common keyboard and pointer (mouse, tablet, etc.). Most workstations tend to only have one keyboard, and therefore, only one display. Larger, multi-user systems, however, will frequently have several displays so that more than one person can be doing graphics work at once. To avoid confusion, each display on a machine is assigned a display number (beginning at 0) when the X server for that display is started. The display number must always be given in a display name. screennumber Some displays share a single keyboard and pointer among two or more monitors. Since each monitor has its own set of windows, each screen is assigned a screen number (beginning at 0) when the X server for that display is started. If the screen number is not given, then screen 0 will be used. On POSIX systems, the default display name is stored in your DISPLAY environment variable. This variable is set automatically by the xterm terminal emulator. However, when you log into another machine on a network, you'll need to set DISPLAY by hand to point to your display. For example, % setenv DISPLAY myws:0 (C Shell) $ DISPLAY=myws:0; export DISPLAY (Korn Shell) The xon script can be used to start an X program on a remote machine; it automatically sets the DISPLAY variable correctly. Finally, most X programs accept a command line option of "-display displayname" to temporarily override the contents of DISPLAY. This is most commonly used to pop windows on another person's screen or as part of a "remote shell" command to start an xterm pointing back to your display. For example, $ xload -display joesws:0 -geometry 100x100+0+0 $ rsh big xterm -display myws:0 -ls

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
Display Names
From the user's perspective, every X server has a display name of the form:
hostname:displaynumber.screennumber
This information is used by the application to determine how it should connect to the server and which
screen it should use by default (on displays with multiple monitors):
hostname
The hostname specifies the name of the machine to which the display is physically connected. If
the hostname is not given, the most efficient way of communicating to a server on the same
machine will be used.
displaynumber
The phrase "display" is usually used to refer to the collection of monitors that share a common
keyboard and pointer (mouse, tablet, etc.). Most workstations tend to only have one keyboard,
and therefore, only one display. Larger, multi-user systems, however, will frequently have
several displays so that more than one person can be doing graphics work at once. To avoid
confusion, each display on a machine is assigned a display number (beginning at 0) when the X
server for that display is started. The display number must always be given in a display name.
screennumber
Some displays share a single keyboard and pointer among two or more monitors. Since each
monitor has its own set of windows, each screen is assigned a screen number (beginning at 0)
when the X server for that display is started. If the screen number is not given, then screen 0 will
be used.
On POSIX systems, the default display name is stored in your
DISPLAY
environment variable. This
variable is set automatically by the xterm terminal emulator. However, when you log into another
machine on a network, you'll need to set
DISPLAY
by hand to point to your display. For example,
% setenv DISPLAY myws:0
(C Shell)
$ DISPLAY=myws:0; export DISPLAY
(Korn Shell)
The
xon
script can be used to start an X program on a remote machine; it automatically sets the
DISPLAY
variable correctly.
Finally, most X programs accept a command line option of "
-display displayname
" to temporarily
override the contents of
DISPLAY
. This is most commonly used to pop windows on another person's
screen or as part of a "remote shell" command to start an xterm pointing back to your display. For
example,
$ xload -display joesws:0 -geometry 100x100+0+0
$ rsh big xterm -display myws:0 -ls </dev/null &
X servers listen for connections on a variety of different communications channels (network byte
streams, shared memory, etc.). Since there can be more than one way of contacting a given server, the
Graphics Administration Guide for HP-UX 10.20
Page 128