![Teledyne Dock Server User Manual Download Page 135](http://html.mh-extra.com/html/teledyne/dock-server/dock-server_user-manual_1080796135.webp)
Revision 7.10
2/28/2012
Each time a glider initiates communication with Dock Server, it treats the glider as if its
name is “unknown” until Dock Server determines the glider’s real name. Thus, the
unknown glider’s icon in Glider Terminal may momentarily turn green. To determine a
glider’s name, Dock Server continually monitors glider output for the string “Vehicle
Name:”. A glider’s name always immediately follows this string. The glider outputs this
string with its name each time it boots, each time it connects by freewave and iridium,
each time it outputs the surface dialog, and in response to the whoRu command
(available in picoDOS, gliderDOS, science, and mission surfaces). Upon initially
connecting, Dock Server attempts to detect the glider’s name in its output. If not
detected after a short period, Dock Server sends a single whoRu command. This
causes the glider to respond with its name and Dock Server detects it. Once detected,
the “unknown” glider icon turns red and the icon corresponding to the detected glider
turns green.
Occasionally, a glider can not respond to the whoRu command at the time Dock Server
sends it. In this case, Dock Server continues to treat the glider as the glider “unknown”
and to monitor its output for its real name. Users may interact with this unknown glider
by opening its glider tab and treating it as they would any other glider. It is strongly
recommended that the only user interaction with an unknown glider be to identify the
glider to Dock Server. That is, when the glider can accept user commands, the user
should enter the whoRu command. This will force Dock Server to recognize the glider.
Otherwise, all files transferred to and from this glider will be stored in the unknown
glider’s toglider and fromglider directories.
11.5 Dock Server Machine User Accounts
Table 115 details the four user accounts related to Dock Server’s use as a glider
mission control machine. These accounts have different privileges appropriate to their
purpose. Refer to Appendix D for the factory delivered passwords to these accounts.
User Account
Purpose
dockserver
The Dock Server application runs as this user. No user login
allowed.
dataserver
The Data Server application runs as this user. No user login
allowed.
dockserveruser
Set up for FTP transfer of glider files. The application, gmcFTP,
uses this account to FTP files. No user login allowed.
Page 135 of 228