source: trunk/athena/bin/attach/detach.1 @ 5752

Revision 5752, 4.9 KB checked in by probe, 33 years ago (diff)
corrected wording about -lint option
Line 
1.\" $Id: detach.1,v 1.5 1992-01-06 15:54:11 probe Exp $
2.\"
3.TH DETACH 1 "1 July 1991"
4.ds ]W MIT Project Athena
5.SH NAME
6detach \- detach a remote file system from your workstation
7.SH SYNOPSIS
8.nf
9detach [ options ] filesystem or mountpoint ...
10detach -a [ options ]
11.SH DESCRIPTION
12
13\fIDetach\fP performs the appropriate device-dependent operations to
14disassociate a filesystem which was attached using \fIattach\fP(1)
15from the workstation. 
16
17The second form is used to detach all attached filesystems from the
18workstation.  This is typically run when the workstation
19deactivates, so as to flush all user mounted filesystems from the
20workstation.
21
22The following options are available in \fIdetach\fP:
23
24.IP "-verbose or -v"
25Display verbose information about the success of the detach.  This is
26the default.
27.IP "-quiet or -q"
28Don't display verbose information.
29.IP "-all or -a"
30Attempt to detach all filesystems which had been attached using the
31\fIattach\fP command.
32.IP "-debug or -d"
33Print debugging information.  This will not normally be useful to users.
34.IP "-unmap or -y"
35Attempt to remove authentication for the user from the filesystem
36server.  The authentication will be removed even if the detach fails.
37This is the default.
38.IP "-nomap or -n"
39Do not attempt to remove authentication for the user from the
40filesystem server.
41.IP "-zephyr or -z"
42Remove \fIZephyr\fP subscription information about the server host.
43.IP "-nozephyr or -h"
44Don't remove \fIZephyr\fP subscription information about the server host.
45.IP "-type \fIfilesystem-type\fP or -t \fIfilesystem-type\fP"
46Used with the -all option to detach all filesystems of a particular
47type.  If not specified, the -all option will detach all filesystems.
48.IP "-explicit or -e"
49Change the behavior of \fIdetach\fP such that the \fIfilesystem\fP is
50now interpreted as \fIhost:directory\fP (in the case of NFS) or
51\fIhost:pack\fP (in the case of RVD) instead of as a Hesiod name.
52Type -type option can be used to specify the filesystem type.
53.IP "-noexplicit or -x"
54Tell \fIdetach\fP to interpret the \fIfilesystem\fP as a Hesiod name.
55This is the default.
56.IP "-force or -f"
57Ordinarily, \fIdetach\fP will not attempt to detach a filesystem which
58it believes it thinks is being attached or detached by another
59process.  This flag overrides this behavior and \fIforces\fP the
60filesystem to be detached.  This option can be dangerous if used
61indiscriminately.
62.IP "-override or -O"
63This option allows the trusted users to force a filesystem to be
64detached, even if it was attached by another user or locked.
65.IP "-host \fIhost\fP or -H \fIhost\fP"
66Requests detach to detach all remote filesystems whose fileserver
67matches the specified host.
68.IP "-user \fIusername\fP or -U \fIusername\fP"
69Trusted users may specify that the \fIdetach\fP command be run on behalf
70of the specified user.
71.IP "-clean or -C"
72This option indicates that the specified filesystems should be detached
73if they are not wanted by anyone who is in \fI/etc/passwd\fP.
74.IP "-lint or -L"
75This option indicates that \fIdetach\fP should delete any malformed
76entries in the \fIattachtab\fP file.
77
78.PP
79The first thing \fIdetach\fP does is to attempt to read in
80/etc/athena/attach.conf, which can be used by the system administrator to
81customize the behavior of \fIattach\fP and \fIdetach\fP.  See
82\fIattach.conf(5)\fP for more information.
83
84.SH DIAGNOSTICS
85
86If \fIdetach\fP is executed with only a single
87filesystem argument, the exit status will be one of the following:
88.TP 5
890
90No error encountered.
91.TP 5
921
93Bad arguments.
94.TP 5
953
96Internal fatal error.
97.TP 5
9810
99Keberos failure.
100.TP 5
10111
102Host communication failure.
103.TP 5
10412
105Authentication failure.
106.TP 5
10713
108No reserved ports available.
109.PP
110.TP 5
11120
112Filesystem not attached.
113.TP 5
11421
115Filesystem already in use by another \fIdetach\fP process.
116.PP
117If more than one filesystem argument is specified (or \fIdetach\fP is
118executed with the -a option), the exit status can be either 0, 1, or 3
119as listed above, or:
120.TP 5
1212
122Something went wrong with one of the filesystems.
123.PP
124If an error is encountered while manipulating one filesystem in the
125list, \fIdetach\fP continues with the other filesystems and returns
126the exit status 2 after attempting to detach all the other filesystems.
127
128.SH NOTE
129The programs \fIattach(1)\fP, \fIdetach(1)\fP, \fInfsid(1)\fP, and
130\fIzinit(8)\fP are all really the same program.  Typically
131\fIdetach(1)\fP, \fInfsid(1)\fP and \fIzinit(8)\fP are links to
132\fIattach\fP.  Argv[0] is used to determine which one of the four
133programs are run.  This may be overridden by specifying -P
134\fIprogname\fP, where \fIprogname\fP should be one of the above four
135program names.
136
137.SH FILES
138/usr/tmp/attachtab
139.br
140/tmp/attach.\fIfilesystem\fP
141
142.SH "SEE ALSO"
143
144attach(1), nfsid(1), zinit(8), zephyr(1), hesiod(3)
145.br
146`Hesiod - Project Athena Technical Plan -- Name Service'
147.br
148`Hesiod Applications Programmers' Guide'
149.br
150`Hesiod Operations and Maintenance Guide'
151
152.SH AUTHOR
153Robert French, Project Athena
154.br
155Copyright 1988, Massachusetts Institute of Technology
156
157.SH BUGS
Note: See TracBrowser for help on using the repository browser.