HP t505 Administrator Guide 7 - Page 161

root > sshd, root > time

Get HP t505 PDF manuals and user guides View all HP t505 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 161 highlights

root > sshd Table E-35 root > sshd Registry key root/sshd/enabled root/sshd/userAccess root > time Table E-36 root > time Registry key root/time/NTPServers root/time/TimeServerIPAddress root/time/WebServerURL root/time/timezone root/time/use24HourFormat root/time/useDHCPTimezone root/time/useNTPServers Description If set to 1, the SSH daemon is enabled and the thin client can be accessed via SSH. If set to 1, standard users can connect to the thin client via SSH. Description Specifies NTP servers to use via a comma-separated list. Private NTP servers or large virtual NTP clusters such as pool.ntp.org are the best choices to minimize server load. Clear this value to return to using DHCP servers (tag 42) instead of a fixed list. Sets the time server used by the Linux net command. These servers are typically the domain controller servers on the corporate network. This should be used when NTP servers are not configured or they are not responding. The Linux net command identifies this server on its own. However, specific server IP addresses can be provided here if desired. Sets the web server URL (such as hp.com) to use when fetching the time using the http protocol. This URL can be within an intranet or over the Internet. Sets the time zone. Time zones should be specified as defined by Linux Timezone in the Date and Time utility in the Control Panel, and they should be in the following format: / . If set to -1, the system chooses the format automatically according to the locale. If set to 0, the a.m./p.m. format is used. If set to 1, the 24-hour format is used. If set to 1, the thin client will attempt to set the time zone via DHCP. To properly set the time zone via this registry key, ensure that the DHCP server for the thin client forwards the tcode DHCP tag (which is usually tag 101, although 100 and 2 can work also). If set to 1, the use of NTP time servers to synchronize the thin client clock is enabled. If this is enabled, ensure that an NTP server is specified via DHCP or via NTPServers. root > sshd 149

  • 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
root > sshd
Table E-35
root > sshd
Registry key
Description
root/sshd/enabled
If set to 1, the SSH daemon is enabled and the thin client can be
accessed via SSH.
root/sshd/userAccess
If set to 1, standard users can connect to the thin client via SSH.
root > time
Table E-36
root > time
Registry key
Description
root/time/NTPServers
Specifies
NTP servers to use via a comma-separated list. Private
NTP servers or large virtual NTP clusters such as
pool.ntp.org
are the best choices to minimize server load.
Clear this value to return to using DHCP servers (tag 42) instead of
a
fixed
list.
root/time/TimeServerIPAddress
Sets the time server used by the Linux
net
command. These
servers are typically the domain controller servers on the
corporate network. This should be used when NTP servers are not
configured
or they are not responding. The Linux
net
command
identifies
this server on its own. However,
specific
server IP
addresses can be provided here if desired.
root/time/WebServerURL
Sets the web server URL (such as
hp.com
) to use when fetching
the time using the http protocol. This URL can be within an
intranet or over the Internet.
root/time/timezone
Sets the time zone. Time zones should be
specified
as
defined
by
Linux Timezone
in the
Date and Time
utility in the Control Panel,
and they should be in the following format:
<region>/
<subregion>
.
root/time/use24HourFormat
If set to -1, the system chooses the format automatically
according to the locale. If set to 0, the a.m./p.m. format is used. If
set to 1, the 24-hour format is used.
root/time/useDHCPTimezone
If set to 1, the thin client will attempt to set the time zone via
DHCP. To properly set the time zone via this registry key, ensure
that the DHCP server for the thin client forwards the
tcode
DHCP
tag (which is usually tag 101, although 100 and 2 can work also).
root/time/useNTPServers
If set to 1, the use of NTP time servers to synchronize the thin
client clock is enabled. If this is enabled, ensure that an NTP
server is
specified
via DHCP or via
NTPServers
.
root > sshd
149