Import Upstream version 1.8.5
[hcoop/debian/openafs.git] / doc / man-pages / pod8 / ptserver.pod
CommitLineData
805e021f
CE
1=head1 NAME
2
3ptserver - Initializes the Protection Server
4
5=head1 SYNOPSIS
6
7=for html
8<div class="synopsis">
9
10ptserver S<<< [B<-database> | B<-db> <I<db path>>] >>>
11 S<<< [B<-p> <I<number of threads>>] >>>
12 S<<< [B<-d> <I<debug level>>] >>>
13 S<<< [B<-groupdepth> | B<-depth> <I<# of nested groups>>] >>>
14 S<<< [B<-default_access> <I<user access mask>> <I<group access mask>>] >>>
15 [B<-restricted>] [B<-restrict_anonymous>] [B<-enable_peer_stats>]
16 [B<-enable_process_stats>] [B<-allow-dotted-principals>]
17 [B<-rxbind>] S<<< [B<-auditlog> <I<file path>>] >>>
18 S<<< [B<-audit-interface> (file | sysvmq)] >>>
19 S<<< [B<-syslog>[=<I<FACILITY>>]] >>>
20 S<<< [B<-logfile> <I<log file>>] >>>
21 [B<-transarc-logs>]
22 S<<< [B<-config> <I<configuration path>>] >>>
23 S<<< [B<-rxmaxmtu> <I<bytes>>] >>>
24 [B<-help>]
25
26=for html
27</div>
28
29=head1 DESCRIPTION
30
31The B<ptserver> command initializes the Protection Server, which must run
32on every database server machine. In the conventional configuration, its
33binary file is located in the F</usr/afs/bin> directory on a file server
34machine.
35
36The ptserver command is not normally issued at the command shell prompt,
37but rather placed into a database server machine's
38F</usr/afs/local/BosConfig> file with the B<bos create> command. If it is
39ever issued at the command shell prompt, the issuer must be logged onto a
40file server machine as the local superuser C<root>.
41
42The Protection Server performs the following tasks:
43
44=over 4
45
46=item *
47
48Maintains the Protection Database, which contains entries for every user
49and group in the cell. Use the B<pts> commands to administer the database.
50
51=item *
52
53Allocates AFS IDs for new user, machine and group entries and maps each ID
54to the corresponding name.
55
56=item *
57
58Generates a current protection subgroup (CPS) at the File Server's
59request. The CPS lists all groups to which a user or machine belongs.
60
61=back
62
63When using Kerberos 5, cross-realm authentication is possible. If the
64special pts group system:authuser@FOREIGN.REALM exists and its group quota
65is greater than zero, B<aklog> will automatically create an entry for the
66foreign user in the local PTS database and add the foreign user to the
67system:authuser@FOREIGN.REALM PTS group. Each time a foreign user is
68created in the local PTS database, the group quota for the
69system:authuser@FOREIGN.REALM PTS group is decremented by one.
70
71This command does not use the syntax conventions of the AFS command
72suites. Provide the command name and all option names in full.
73
74=head1 OPTIONS
75
76=over 4
77
78=item B<-d> <I<debug level>>
79
80Sets the detail level for the debugging trace written to the
81F</usr/afs/logs/PtLog> file. Provide one of the following values, each
82of which produces an increasingly detailed trace: C<0>, C<1>, C<5>, C<25>,
83and C<125>.
84
85=item B<-database> | B<-db> <I<db path>>
86
87Specifies the pathname of an alternate directory in which the Protection
88Database files reside. Provide the complete pathname, ending in the base
89filename to which the C<.DB0> and C<.DBSYS1> extensions are appended. For
90example, the appropriate value for the default database files is
91F</usr/afs/db/prdb>.
92
93=item B<-p> <I<number of threads>>
94
95Sets the number of server lightweight processes (LWPs or pthreads) to run.
96Provide a positive integer from the range C<3> to C<64>. The default
97value is C<3>.
98
99=item B<-groupdepth> | B<-depth> <I<# of nested groups>>
100
101Specifies the group depth for nested groups when B<ptserver> is compiled
102with the SUPERGROUPS option enabled. The default depth for nested groups
103is 5.
104
105=item B<-default_access> <I<user access>> <I<group access>>
106
107Specifies the default user and group privacy flags to apply to each
108entry. Provide a string of five characters, one for each of the
109permissions. See L<pts_examine(1)> or L<pts_setfields(1)> for more
110information on the flags.
111
112=item B<-restricted>
113
114Run the PT Server in restricted mode. While in restricted mode, only
115members of the system:administrators PTS group may make any PTS changes.
116
117=item B<-restrict_anonymous>
118
119Run the PT Server in restricted anonymous access mode. While in this mode,
120only authenticated users will be able to access the PTS database.
121
122=item B<-enable_peer_stats>
123
124Activates the collection of Rx statistics and allocates memory for their
125storage. For each connection with a specific UDP port on another machine,
126a separate record is kept for each type of RPC (FetchFile, GetStatus, and
127so on) sent or received. To display or otherwise access the records, use
128the Rx Monitoring API.
129
130=item B<-enable_process_stats>
131
132Activates the collection of Rx statistics and allocates memory for their
133storage. A separate record is kept for each type of RPC (FetchFile,
134GetStatus, and so on) sent or received, aggregated over all connections to
135other machines. To display or otherwise access the records, use the Rx
136Monitoring API.
137
138=item B<-allow-dotted-principals>
139
140By default, the RXKAD security layer will disallow access by Kerberos
141principals with a dot in the first component of their name. This is to
142avoid the confusion where principals user/admin and user.admin are both
143mapped to the user.admin PTS entry. Sites whose Kerberos realms don't have
144these collisions between principal names may disable this check by
145starting the server with this option.
146
147=item B<-rxbind>
148
149Bind the Rx socket to the primary interface only. (If not specified, the
150Rx socket will listen on all interfaces.)
151
152=item B<-syslog>[=<I<syslog facility>>]
153
154Specifies that logging output should go to syslog instead of the normal
155log file. B<-syslog>=I<FACILITY> can be used to specify to which facility
156the log message should be sent. Logging message sent to syslog are tagged
157with the string "ptserver".
158
159=item B<-logfile> <I<log file>>
160
161Sets the file to use for server logging. If logfile is not specified, and
162no other logging options are supplied, this will be F</usr/afs/logs/PtLog>.
163Note that this option is intended for debugging and testing purposes.
164Changing the location of the log file from the command line may result
165in undesirable interactions with tools such as B<bos>.
166
167=item B<-transarc-logs>
168
169Use Transarc style logging features. Rename the log file
170F</usr/afs/logs/PtLog> to F</usr/afs/logs/PtLog.old> when the PT Server is
171restarted. This option is provided for compatibility with older versions.
172
173=item B<-config> <I<configuration directory>>
174
175Set the location of the configuration directory used to configure this
176service. In a typical configuration this will be F</usr/afs/etc> - this
177option allows the use of alternative configuration locations for testing
178purposes.
179
180=item B<-auditlog> <I<log path>>
181
182Turns on audit logging, and sets the path for the audit log. The audit
183log records information about RPC calls, including the name of the RPC
184call, the host that submitted the call, the authenticated entity (user)
185that issued the call, the parameters for the call, and if the call
186succeeded or failed.
187
188=item B<-audit-interface> (file | sysvmq)
189
190Specifies what audit interface to use. Defaults to C<file>. See
191L<fileserver(8)> for an explanation of each interface.
192
193=item B<-rxmaxmtu> <I<bytes>>
194
195Sets the maximum transmission unit for the RX protocol.
196
197=item B<-help>
198
199Prints the online help for this command. All other valid options are
200ignored.
201
202=back
203
204=head1 EXAMPLES
205
206The following B<bos create> command creates a C<ptserver> process on the
207machine C<fs3.example.com>. The command appears here on multiple lines only
208for legibility.
209
210 % bos create -server fs3.example.com -instance ptserver \
211 -type simple -cmd /usr/afs/bin/ptserver
212
213=head1 PRIVILEGE REQUIRED
214
215The issuer must be logged in as the superuser C<root> on a file server
216machine to issue the command at a command shell prompt. It is conventional
217instead to create and start the process by issuing the B<bos create>
218command.
219
220=head1 SEE ALSO
221
222L<BosConfig(5)>,
223L<PtLog(5)>,
224L<prdb.DB0(5)>,
225L<bos_create(8)>,
226L<bos_getlog(8)>,
227L<pts(1)>
228
229=head1 COPYRIGHT
230
231IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
232
233This documentation is covered by the IBM Public License Version 1.0. It was
234converted from HTML to POD by software written by Chas Williams and Russ
235Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.