1 | .\" $Id: attachandrun.1,v 1.1 2000-03-15 20:53:10 ghudson Exp $ |
---|
2 | .\" |
---|
3 | .\" Copyright 1997 by the Massachusetts Institute of Technology. |
---|
4 | .\" |
---|
5 | .\" Permission to use, copy, modify, and distribute this |
---|
6 | .\" software and its documentation for any purpose and without |
---|
7 | .\" fee is hereby granted, provided that the above copyright |
---|
8 | .\" notice appear in all copies and that both that copyright |
---|
9 | .\" notice and this permission notice appear in supporting |
---|
10 | .\" documentation, and that the name of M.I.T. not be used in |
---|
11 | .\" advertising or publicity pertaining to distribution of the |
---|
12 | .\" software without specific, written prior permission. |
---|
13 | .\" M.I.T. makes no representations about the suitability of |
---|
14 | .\" this software for any purpose. It is provided "as is" |
---|
15 | .\" without express or implied warranty. |
---|
16 | .\" |
---|
17 | .TH ATTACHANDRUN 1 |
---|
18 | .SH NAME |
---|
19 | attachandrun \- attach a filesystem and run a program from it |
---|
20 | |
---|
21 | .SH SYNOPSIS |
---|
22 | attachandrun [--check] locker program argv0 [argv1 ...] |
---|
23 | |
---|
24 | .SH DESCRIPTION |
---|
25 | \fIattachandrun\fR combines the operations of attaching a locker, |
---|
26 | locating its binary directory, and executing a program out of that |
---|
27 | directory. Running a program via \fIattachandrun\fR should be |
---|
28 | indistinguishable from running it out of its locker by hand. A typical |
---|
29 | ``attach and run'' script would look like: |
---|
30 | |
---|
31 | .nf |
---|
32 | #!/bin/sh |
---|
33 | exec /bin/athena/attachandrun moira blanche "$0" "$@" |
---|
34 | .fi |
---|
35 | |
---|
36 | If you specify the \fI--check\fR option, \fIattachandrun\fR will check |
---|
37 | for the existence of the binary but not actually run it. (In this |
---|
38 | case, you don't need to specify any argv elements.) It will exit with |
---|
39 | status 0 if the binary exists, or 1 if it does not. Note that a |
---|
40 | successful exit status does not necessarily mean that attempting to |
---|
41 | run the binary will succeed: it indicates only that the file exists. |
---|
42 | |
---|
43 | .SH "SEE ALSO" |
---|
44 | attach(1), add(1) |
---|
45 | |
---|
46 | .SH AUTHORS |
---|
47 | Craig Fields, MIT Information Systems |
---|
48 | Dan Winship, MIT Information Systems |
---|
49 | .PP |
---|
50 | Copyright 1998 Massachusetts Institute of Technology |
---|