Mknf and rmnf create and delete notesfiles respectively. The same parameters apply for each: the `topic' is the name that the notesfile is
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
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.
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.
/usr/spool/notes/.utilities where these programs live.
/usr/spool/notes Default notesfile directory.
Ray Essick (uiucdcs!essick, firstname.lastname@example.org)
Department of Computer Science
University of Illinois at Urbana-Champaign
Rob Kolstad (kolstad@convex.UUCP)
CONVEX Computer Corporation
University of Illinois MKNF(8)
All times are GMT -4. The time now is 11:27 PM.
Unix & Linux Forums Content Copyright 1993-2018. All Rights Reserved.