2005-12-08 12:14:33 +00:00
|
|
|
=over 4
|
|
|
|
|
2008-08-25 03:14:39 +01:00
|
|
|
=item B<-d> <I<debug level>>
|
|
|
|
|
|
|
|
Sets the detail level for the debugging trace written to the
|
|
|
|
F</usr/afs/logs/VolserLog> file. Provide one of the following values, each
|
|
|
|
of which produces an increasingly detailed trace: C<0>, C<1>, C<5>, C<25>,
|
|
|
|
and C<125>.
|
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
=item B<-log>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
Records in the /usr/afs/logs/VolserLog file the names of all users who
|
|
|
|
successfully initiate a B<vos> command. The Volume Server also records any
|
|
|
|
file removals that result from issuing the B<vos release> command with the
|
|
|
|
B<-f> flag.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
=item B<-p> <I<number of processes>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
Sets the number of server lightweight processes (LWPs) to run. Provide an
|
|
|
|
integer between C<4> and C<16>. The default is C<9>.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2009-06-24 22:46:27 +01:00
|
|
|
=item B<-auditlog> <I<log path>>
|
|
|
|
|
2009-07-25 18:37:08 +01:00
|
|
|
Turns on audit logging, and sets the path for the audit log. The audit
|
2009-07-27 02:26:59 +01:00
|
|
|
log records information about RPC calls, including the name of the RPC
|
2009-07-25 18:37:08 +01:00
|
|
|
call, the host that submitted the call, the authenticated entity (user)
|
|
|
|
that issued the call, the parameters for the call, and if the call
|
|
|
|
succeeded or failed.
|
2009-06-24 22:46:27 +01:00
|
|
|
|
|
|
|
=item B<-audit-interface> (file | sysvmq)
|
|
|
|
|
|
|
|
Specifies what audit interface to use. Defaults to C<file>. See
|
|
|
|
L<fileserver(8)> for an explanation of each interface.
|
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
=item B<-udpsize> <I<size of socket buffer>>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
Sets the size of the UDP buffer in bytes, which is 64 KB by
|
|
|
|
default. Provide a positive integer, preferably larger than the default.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2008-08-25 03:14:39 +01:00
|
|
|
=item B<-jumbo>
|
|
|
|
|
|
|
|
Allows the server to send and receive jumbograms. A jumbogram is
|
|
|
|
a large-size packet composed of 2 to 4 normal Rx data packets that share
|
|
|
|
the same header. The volserver does not use jumbograms by default, as some
|
|
|
|
routers are not capable of properly breaking the jumbogram into smaller
|
|
|
|
packets and reassembling them.
|
|
|
|
|
|
|
|
=item B<-nojumbo>
|
|
|
|
|
|
|
|
Deprecated; jumbograms are disabled by default.
|
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
=item B<-enable_peer_stats>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Activates the collection of Rx statistics and allocates memory for their
|
2005-12-13 19:21:13 +00:00
|
|
|
storage. For each connection with a specific UDP port on another machine,
|
|
|
|
a separate record is kept for each type of RPC (FetchFile, GetStatus, and
|
|
|
|
so on) sent or received. To display or otherwise access the records, use
|
|
|
|
the Rx Monitoring API.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
=item B<-enable_process_stats>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
Activates the collection of Rx statistics and allocates memory for their
|
|
|
|
storage. A separate record is kept for each type of RPC (FetchFile,
|
|
|
|
GetStatus, and so on) sent or received, aggregated over all connections to
|
|
|
|
other machines. To display or otherwise access the records, use the Rx
|
|
|
|
Monitoring API.
|
|
|
|
|
2009-05-05 14:30:24 +01:00
|
|
|
=item B<-allow-dotted-principals>
|
2008-01-23 04:13:55 +00:00
|
|
|
|
|
|
|
By default, the RXKAD security layer will disallow access by Kerberos
|
|
|
|
principals with a dot in the first component of their name. This is to avoid
|
|
|
|
the confusion where principals user/admin and user.admin are both mapped to the
|
|
|
|
user.admin PTS entry. Sites whose Kerberos realms don't have these collisions
|
|
|
|
between principal names may disable this check by starting the server
|
|
|
|
with this option.
|
|
|
|
|
2012-02-23 17:34:44 +00:00
|
|
|
=item B<-preserve-vol-stats>
|
|
|
|
|
|
|
|
Preserve volume access statistics over volume restore and reclone operations.
|
|
|
|
By default, volume access statistics are reset during volume restore and reclone
|
|
|
|
operations.
|
|
|
|
|
Make ihandle sync behavior runtime-configurable
The actual behavior of FDH_SYNC has changed a bit over the years, and
some people want one behavior, and some want another. Make it possible
to make this choice at runtime with the new -sync option, instead of
making this decision by running with different patches.
Note that FDH_SYNC is not a macro anymore, nor is it an inline
function. While it could be a macro, it would look a bit complex, and
there are some oddities with trying to use vol_io_params inside the
FDH_SYNC expansion (vol_io_params is not declared for LWP, for
example). And having it be an inline function causes problems with
some odd linking dependencies. For example, vlib.a contains volume.o,
but does not contain a definition for DFlushVolume (dir/buffer.c),
which is referenced in volume.o. 'vos' uses vlib.a, but does not
bring in anything that defines DFlushVolume. Currently this appears to
not cause a problem because 'vos' uses nothing from volume.o, so the
dependencies of volume.o don't matter. Adding an inline FDH_SYNC for
platforms that don't support 'static inline' would add a dependency to
volume.o (via vol_io_params), which causes an error for the lack of a
DFlushVolume.
Those are possibly just some problems, and may not be all. So instead,
make it so we don't have to deal with that and just have a normal
function. While FDH_SYNC may be called in a performance-critical
section, the overhead of a real function call is nowhere near the
delay of an actual fsync(), so presumably any overhead doesn't matter.
Change-Id: I23620bd8ac31b9019e9d55cb46ec9f3a75f5675c
Reviewed-on: http://gerrit.openafs.org/9694
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Derrick Brashear <shadow@your-file-system.com>
2013-03-29 18:40:41 +00:00
|
|
|
=item B<-sync> <I<sync behavior>>
|
|
|
|
|
|
|
|
This is the same as the B<-sync> option in L<fileserver(8)>. See
|
|
|
|
L<fileserver(8)>.
|
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
=item B<-help>
|
2005-12-08 12:14:33 +00:00
|
|
|
|
2005-12-13 19:21:13 +00:00
|
|
|
Prints the online help for this command. All other valid options are
|
|
|
|
ignored.
|
2005-12-08 12:14:33 +00:00
|
|
|
|
|
|
|
=back
|