|
|
1.1 ! root 1: .TH "XNSARCHIVE" 1 "3-MAR-87" "Xerox (WRC)" ! 2: .\" $Header: xnsarchive.n,v 1.1 87/04/01 13:56:18 ed Exp $ ! 3: .SH NAME ! 4: xnsarchive - Archive facility for XNS file servers ! 5: .SH SYNOPSIS ! 6: .B xnsarchive ! 7: [ ! 8: .B \-u ! 9: ] [ ! 10: .B \-v ! 11: ] [ ! 12: .B -l log-file ! 13: ] ! 14: .B remote-file local-file ! 15: .SH DESCRIPTION ! 16: .I Xnsarchive ! 17: serializes the file named in \fIremote-file\fR into the file on the local ! 18: host named by \fIlocal-file\fR. The serialized format maintains both content ! 19: and attributes for the remote file and any descendant files if the file is ! 20: a directory. The resulting file can then be written to tape for archival ! 21: purposes. ! 22: .PP ! 23: If \fIlocal-file\fR is \*(lq-\*(rq, then the output will be written to ! 24: \fIstdout\fR. This is useful for piping to other programs directly. ! 25: .PP ! 26: The arguments specified in \fIremote-file1\fR may be in one ! 27: of the following three forms, where host is a Clearinghouse name of the form ! 28: \fIobject:domain:organization\fR (domain and organization are optional): ! 29: .nf ! 30: [host]filename ! 31: (host)filename ! 32: host:filename ! 33: .fi ! 34: .PP ! 35: Credentials for accessing the remote service are determined either from the ! 36: environment variables XNSNAME and XNSPASSWD or, if not defined, by prompting ! 37: the user. ! 38: .PP ! 39: The possible options are: ! 40: .TP ! 41: .BI -l \ log-file ! 42: causes a summary of all files archived to be written to \fIlog-file\fR. ! 43: .TP ! 44: .B -u ! 45: causes the access list of the file named in \fIremote-file\fR to be propogated ! 46: to all descendants to eliminate potential access conflicts during ! 47: serialization. ! 48: .TP ! 49: .B -v ! 50: causes informational messages to be written to \fIstderr\fR along the way. ! 51: .SH "SEE ALSO" ! 52: xnsrestore(1N), xnscreds(1N) ! 53: .br ! 54: Filing Protocol, \s8XSIS\s0 108605 (May 1986) ! 55: .SH AUTHORS ! 56: Ed Flint ! 57:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.