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

Atom Control, Notes, Origin, See Also, The Open Group

Page 159 highlights

Atom Control At startup, lbxproxy "pre-interns" a configurable list of atoms. This allows lbxproxy to intern a group of atoms in a single round trip and immediately store the results in its cache. While running, lbxproxy uses heuristics to decide when to delay sending window property data to the server. The heuristics depend on the size of the data, the name of the property, and whether a window manager is running through the same lbxproxy. Atom control is specified in the /etc/X11/lbxproxy/AtomControl file, set up during installation of lbxproxy, with command-line overrides. The file is a simple text file. There are three forms of lines: comments, length control, and name control. Lines starting with a "!" are treated as comments. A line of the form z specifies the minimum length in bytes before property data will be delayed. A line of the form controls the given atom, where is any combination of the following characters: "i" means the atom should be pre-interned; "n" means data for properties with this name should never be delayed; and "w" means data for properties with this name should be delayed only if a window manager is also running through the same lbxproxy. Notes When the authorization protocol XDM-AUTHORIZATION-1 is used: A client must be on the same host as lbxproxy for the client to be authorized to connect to the server. If a client is not on the same host as lbxproxy, the client will not be authorized to connect to the server. Origin The Open Group See Also proxymngr(1), xfindproxy(1) Page 159 Graphics Administration Guide for HP-UX 10.20

  • 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

Atom Control
At startup,
lbxproxy
"pre-interns" a configurable list of atoms. This allows
lbxproxy
to intern a group of
atoms in a single round trip and immediately store the results in its cache.
While running,
lbxproxy
uses heuristics to decide when to delay sending window property data to the
server. The heuristics depend on the size of the data, the name of the property, and whether a window
manager is running through the same
lbxproxy
.
Atom control is specified in the
/etc/X11/lbxproxy/AtomControl
file, set up during installation of
lbxproxy
, with command-line overrides.
The file is a simple text file. There are three forms of lines: comments, length control, and name control.
Lines starting with a "!" are treated as comments. A line of the form
z <length>
specifies the minimum length in bytes before property data will be delayed. A line of the form
<options> <atomname>
controls the given atom, where <options> is any combination of the following characters: "
i
" means the
atom should be pre-interned; "
n
" means data for properties with this name should never be delayed; and
"
w
" means data for properties with this name should be delayed only if a window manager is also
running through the same
lbxproxy
.
Notes
When the authorization protocol
XDM-AUTHORIZATION-1
is used:
A client must be on the same host as
lbxproxy
for the client to be authorized to connect to the server.
If a client is not on the same host as
lbxproxy
, the client will not be authorized to connect to the server.
Origin
The Open Group
See Also
proxymngr(1),
xfindproxy(1)
Graphics Administration Guide for HP-UX 10.20
Page 159