HP Z620 HP Remote Graphics Software 5.4.7 - Page 182

Setting properties on the command line, Authenticator properties, rgreceiver.sh -Rgreceiver.IsSnap = 1

Page 182 highlights

The configuration files contain property name/value pairs, with only one property per line. Empty lines (containing only whitespace characters) are ignored. The "#" character begins a comment on the line, extending to the end of the line. If a property is listed more than once, the value of the last entry is used. NOTE: All properties in the configuration files are initially commented out with the "#" character. To set a property in a configuration file, first delete the "#" character preceding the property name, and then set the property to the desired value. NOTE: RGS properties set in a configuration file do not take affect until the associated program is restarted. For example, if the rgreceiverconfig file is changed, the Receiver should be restarted. Likewise, if the rgsenderconfig file is changed, the Sender should be restarted. Setting properties on the command line Properties can also be set on the command line when the Receiver and Sender are started. Property values entered on the command line override any properties set with other methods. All properties must begin with a "-" on the command line to be recognized as a valid property. For example (on Linux): rgreceiver.sh -Rgreceiver.Network.Timeout.Warning=10000 This command will start the RGS Receiver with the Rgreceiver.Network.Timeout.Warning property set to 10,000 milliseconds (10 seconds). If any property is set more than once on the command line, the value of the last entry is used. No whitespace characters are allowed between the property name, the "=" character, and the property value. For example: rgreceiver.sh -Rgreceiver.IsSnap = 1 This property declaration is invalid because of the whitespace on both sides of the "=" character. Properties of type int vector cannot be set on the command line. CAUTION: If a property name is misspelled, no user notification is provided, and the misspelled property will not take effect. If you specify a property in a configuration file or on a command line, and it does not appear to take effect, first verify that the property name is spelled correctly and that upper/ lower case usage is correct. Authenticator properties The following Sender and Receiver properties affect how the user authenticates an RGS connection: Rgsender.LoggedInAuthenticators Rgsender.LoggedOutAuthenticators Rgreceiver.AuthenticatorId Rgreceiver.AuthenticatorId.IsMutable CAUTION: The authenticator properties are typically set by 3rd party software modules integrated with RGS, and should not be changed. Changing these properties can have unexpected consequences, including preventing you from establishing an RGS connection from the Receiver to the Sender. Therefore, these properties are not listed nor described in the next two sections on user-settable RGS Receiver and Sender properties. 166 Chapter 8 RGS properties

  • 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
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247

The configuration files contain property name/value pairs, with only one property per line. Empty lines
(containing only whitespace characters) are ignored. The "#" character begins a comment on the line,
extending to the end of the line. If a property is listed more than once, the value of the last entry is
used.
NOTE:
All properties in the configuration files are initially commented out with the “#” character. To
set a property in a configuration file, first delete the “#” character preceding the property name, and
then set the property to the desired value.
NOTE:
RGS properties set in a configuration file do not take affect until the associated program is
restarted. For example, if the rgreceiverconfig file is changed, the Receiver should be restarted.
Likewise, if the rgsenderconfig file is changed, the Sender should be restarted.
Setting properties on the command line
Properties can also be set on the command line when the Receiver and Sender are started. Property
values entered on the command line override any properties set with other methods. All properties must
begin with a "-" on the command line to be recognized as a valid property. For example (on Linux):
rgreceiver.sh -Rgreceiver.Network.Timeout.Warning=10000
This command will start the RGS Receiver with the Rgreceiver.Network.Timeout.Warning property set to
10,000 milliseconds (10 seconds). If any property is set more than once on the command line, the
value of the last entry is used. No whitespace characters are allowed between the property name, the
"=" character, and the property value. For example:
rgreceiver.sh -Rgreceiver.IsSnap = 1
This property declaration is invalid because of the whitespace on both sides of the "=" character.
Properties of type int vector cannot be set on the command line.
CAUTION:
If a property name is misspelled, no user notification is provided, and the misspelled
property will not take effect. If you specify a property in a configuration file or on a command line, and
it does not appear to take effect, first verify that the property name is spelled correctly and that upper/
lower case usage is correct.
Authenticator properties
The following Sender and Receiver properties affect how the user authenticates an RGS connection:
Rgsender.LoggedInAuthenticators
Rgsender.LoggedOutAuthenticators
Rgreceiver.AuthenticatorId
Rgreceiver.AuthenticatorId.IsMutable
CAUTION:
The authenticator properties are typically set by 3rd party software modules integrated
with RGS, and should not be changed. Changing these properties can have unexpected consequences,
including preventing you from establishing an RGS connection from the Receiver to the Sender.
Therefore, these properties are not listed nor described in the next two sections on user-settable RGS
Receiver and Sender properties.
166
Chapter 8
RGS properties