Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #487
Difficulty: Easy
A program's entry point is always defined by a main function or method.
True or False?
Linux & Unix Commands - Search Man Pages

nfarchive(8) [bsd man page]

NFARCHIVE(8)						      System Manager's Manual						      NFARCHIVE(8)

NAME
nfarchive - archive notesfiles SYNOPSIS
nfarchive [ -# ] [ -d ] [ -m- or -m+ ] [ -w# ] [ -f file ] topic [ ... ] DESCRIPTION
Nfarchive is used to expire notes that have not been modified in a certain amount of time. Archives are stored in ``archive notesfiles''. The -# parameter is the number of days a notestring must be idle (no new responses) before being eligible for archival. Expired notestrings are either deleted or placed in an archive. The -d parameter tells nfarchive to delete expired notestrings. If unse- lected, the expired notestrings are placed in an archive. The -m+ option specifies that only notes marked with a director message are eligible for expiration. -m- specifies that only notes without a director message are eligible for expiration. By default, the expiration algorithm is indifferent to a note's director message status. The -w# option specified the working set size for the expired notesfiles. The specified number represents the minimum number of notes to leave in the notesfile. The expiration threshold, working set size, expiration action, and director message requirements can all be specified as a director's option in each notesfile. Specific values override what is specified on the nfarchive command line. A default value specifies using the value specified on the command line. The -f parameter specifies a file containing a list of notesfiles to archive. Notesfiles can also be specified on the command line. By default, the archive of notesfile /usr/spool/notes/somenotes is in /usr/spool/oldnotes/somenotes. The archive of /some/other/place/somenotes also defaults to /usr/spool/oldnotes/somenotes. To prevent collisions of this nature, mapping between active and archive notesfiles is implemented. The file /usr/spool/notes/.utilities/net.alias/Archive-into contains lines of the form: active-notesfile:archive notesfile Lines in this file beginning with `#' are comments. Notesfiles without an entry in this file are archived into the /usr/spool/oldnotes directory with the appropriate last component. When initially created, an archive notesfile has an access list matching its active counterpart. Currently, only directors are allowed to write in an archive notesfile. Nfarchive refuses to archive an archive notesfile. FILES
/usr/spool/notes/.utilities where this programs lives. /usr/spool/notes/.utilities/net.alias/Archive-into maps active notesfiles into their archives. /usr/spool/notes Default notes data base /usr/spool/oldnotes Default archive directory SEE ALSO
notes(1), The Notesfile Reference Manual AUTHORS
Ray Essick (uiucdcs!essick, essick%uiuc@csnet-relay.arpa) Department of Computer Science University of Illinois at Urbana-Champaign Urbana, IL Rob Kolstad (kolstad@convex.UUCP) CONVEX Computer Corporation Richardson, TX University of Illinois NFARCHIVE(8)

Check Out this Related Man Page

MKNF(8) 						      System Manager's Manual							   MKNF(8)

NAME
mknf, rmnf - create and delete notesfiles SYNOPSIS
mknf [ -aon ] topic [ ... ] rmnf [ -f ] topic [ ... ] DESCRIPTION
Mknf and rmnf create and delete notesfiles respectively. The same parameters apply for each: the `topic' is the name that the notesfile is known by. As mknf processes its arguments, creating new notesfiles, the name of each new notesfile is echoed to the terminal. The new notesfiles are closed and the notesfile owner is made the sole director. He customarily turns control over to the user requesting the notesfile by making that person a director. The -aon options apply to mknf only. They signify that the notesfiles created are to permit anonymous notes, be open, and be networked respectively. If the file `/usr/spool/notes/.utilities/access-template' is present, it contains a list of access-rights which are added to the created notesfile. The file contains lines of access-rights similar to those used in the nfaccess(8) command. In environments with dynamic cre- ation of notesfiles, such as on USENET nodes, one or more users can automatically be made directors of all new notesfiles. If appropriate, they can be removed from the access list of newly created notesfiles as needed. Rmnf asks for verification of each notesfile before deleting it. The notesfile is deleted if the response line begins with a `y'. If invoked with the -f option, rmnf does not ask for verification before deleting the notesfiles. Only the notesfile owner is allowed to run mknf and rmnf. BUGS
Rmnf doesn't understand about absolute pathnames for notesfiles. It refuses to remove notesfiles specified by absolute pathnames. Any user should be allowed to create private notesfiles in directories where he has permission. FILES
/usr/spool/notes/.utilities where these programs live. /usr/spool/notes/.utilities/access-template Default access-list. /usr/spool/notes Default notesfile directory. SEE ALSO
nfaccess(8), nfxmit(8), notes(1), The Notesfile Reference Manual AUTHORS
Ray Essick (uiucdcs!essick, essick%uiuc@csnet-relay.arpa) Department of Computer Science University of Illinois at Urbana-Champaign Urbana, IL Rob Kolstad (kolstad@convex.UUCP) CONVEX Computer Corporation Richardson, TX University of Illinois MKNF(8)

Featured Tech Videos