Annotation of othersrc/nastore/volman/srvr/rc/vault/vaultrc.1m, Revision 1.1.1.1
1.1 wrstuden 1: .TH VAULTRC 1M "" "" "\s-1NAStore\s+1 Man Pages"
2: .SH NAME
3: vaultrc \- Volume Manager Vault Repository Controller
4: .SH SYNOPSIS
5: .B vaultrc
6: .I rc [\-i]
7: &
8: .SH DESCRIPTION
9: The \fIvaultrc\fR is a \fIvolman\fR(8) Repository Controller (RC)
10: that manages volumes in an operator-controlled vault.
11: If the vaultrc is to be run on the same host as the
12: Volume Manager \fIvold\fR(1M), vold will start
13: it automatically with the \fIrc\fR argument if the
14: PATH variable for the RC is defined in the \fIvold\fR(1M)
15: VCONF file. If vaultrc is started manually, for
16: example on another host than vold, it should be run
17: in the background, and the \fIrc\fR argument must agree
18: with VCONF.
19:
20: The \fIrc\fR argument determines which volumes in the \fIvolman\fR(8)
21: database the process will manage; at NAS, the \fIrc\fR is 2.
22: The optional \fI\-i\fR argument instructs the process not
23: to exit if vold shuts down; instead, the vaultrc will wait
24: and try to reconnect until vold is restarted. When vaultrc
25: reconnects, it reloads the configuration from vold and
26: reinitializes. This option is for convenience when running
27: vaultrc on a non-vold host. Once a vaultrc process has been
28: started in this manner, it can only be shut down using
29: \fIkill\fR(1).
30:
31: The vaultrc gets a list of the drives it manages
32: from the vold, which reads them as part of the
33: RC configuration at startup from its VCONF file.
34: The vaultrc accepts mount requests from the
35: vold and broadcasts operator requests to logins
36: under the console account specified by the SYSLOG
37: statement in VCONF (see below).
38: The vaultrc cooperates with the \fIacsrc\fR(1M) in
39: coordinating moves of cartridge tapes between the
40: ACS Cartridge Entry Ports and the vault.
41:
42: The \fIrcerr\fR(1M) utility is used by operators to fail a request made
43: by a vaultrc.
44:
45: .SH CONFIGURATION
46: This is the vaultrc configuration (format defined in \fIvold\fR(1M))
47: as found in the VCONF file, showing 3490 drives:
48: .nf
49:
50: BEGIN_RC
51: NUMBER 2
52: NAME "Vault RC"
53: ID VAULTRC
54: TYPE VAULTRC
55: LOGIN volman
56: \# SYSLOG: define a console for 'mount xxxxxx on drive yyy'
57: \# requests - normally same as volman error console
58: \# - maps to /etc/syslog.conf entry:
59: \# local0.notice volman
60: SYSLOG LOG_LOCAL0
61: \#
62: \# presence of PATH instructs vold to fork/exec process
63: \#
64: PATH vaultrc
65: CAPACITY -1
66: VARY Vary34X0
67: FLAGS TIMER_MSGS MOUNT_OK ASYNC_UNMOUNT
68: ALLOC_OK RECYCLE_OK NODEMOUNT
69: MEDIA 34X0
70: DRIVES
71: \#
72: \# name dev_num medium channel
73: \#
74: vlt01 1 34X0 39_0
75: END_RC
76: .fi
77:
78: The vaultrc package includes a server that can run on
79: a remote host which manages a database for tracking
80: vault volumes, and broadcasts its own console messages,
81: coordinating with a hand-held bar-code scanner with an
82: LCD display. This part of the package would be vital if
83: vault storage was ever changed to non-serial filing,
84: since it enables the operator to register the location
85: of volumes in the vault by scanning their labels along
86: with vault location labels, as well as providing a
87: readout of requested volumes and their locations on
88: the scanner's LCD. Code for both server and scanner
89: are included; they were tested but have never been used
90: in production.
91:
92: .SH DIAGNOSTICS
93: The vaultrc broadcasts messages to the designated console account.
94:
95: .SH FILES
96: .nf
97:
98: /usr/mss/lib/volman/vaultrc
99: /usr/mss/lib/volman/VCONF
100:
101: .fi
102: .SH SEE ALSO
103: rcerr(1M), vold(1M), volman(8).
CVSweb <webmaster@jp.NetBSD.org>