Tornado

Tornado 2.0
User’s Guide
3.5.2 Sharing and Reserving Target Servers
A target server may be made available to the following classes of user:
– the user who started the server
– a single user, who may or may not have started the server
– a list of specified users
– any user 9
When a target server is available to anyone, its status (shown in the Information
panel of the main launcher window; see Figure 3-3) is unreserved. Any user can
attach a tool to the target, and any user can also restrict its use.
When you configure a target server, you can arrange for the server to be
exclusively available to your user ID every time you launch it, by clicking the Lock
toggle in the Create Target Server form. See 3.5.1 Configuring a Target Server, p.73.
Target servers launched this way have the status locked.
If a target server is not locked by its creator, and if no one else has reserved it, you
can reserve the target server for your own use: click on Target>Reserve, or on the
launcher button. The target status becomes reserved until you release the target
with the Unreserve command ( ). Unreserve on a target that is not reserved has
no effect, nor does Unreserve on a target reserved or locked by someone else.
This simple reserve/unreserve locking mechanism is sufficient for many
development environments. In some organizations, however, it may be necessary
to further restrict some targets to a particular group of users. For example, a Q/A
organization may need to ensure certain targets are used only for testing, while
still using the reserve/unreserve mechanism to manage contention within the
group of testers.
To restrict a target server to a list of users, create a list of authorized users in a file.
The format for the file is the simplest possible: one user name per line. The user
names are host sign-on names, as used by system files like /etc/passwd (or its
network-wide equivalent). You can also use one special entry in the authorization
file: a plus sign + to explicitly authorize any user to connect to the target server.
(This might be useful to preserve the link between a target server and an
9. Strictly speaking, there is another layer of authorization defining who is meant by “any
user”. The file $WIND_BASE/.wind/userlock is a Tornado-wide authorization file, used as
the default list of authorized users for any target server without its own authorized-users
file. The format of this file is the same format described below for individual target-server
authorization files.
82