1MKNF(8)                     System Manager's Manual                    MKNF(8)
2
3
4

NAME

6       mknf, rmnf - create and delete notesfiles
7

SYNOPSIS

9       mknf [ -aon ] topic [ ... ]
10
11       rmnf [ -f ] topic [ ... ]
12

DESCRIPTION

14       Mknf  and  rmnf  create  and  delete notesfiles respectively.  The same
15       parameters apply for each: the `topic' is the name that  the  notesfile
16       is known by.
17
18       As  mknf  processes its arguments, creating new notesfiles, the name of
19       each new notesfile is echoed to the terminal.  The new  notesfiles  are
20       closed and the notesfile owner is made the sole director.  He customar‐
21       ily turns control over to the user requesting the notesfile  by  making
22       that person a director.
23
24       The  -aon options apply to mknf only.  They signify that the notesfiles
25       created are to permit  anonymous  notes,  be  open,  and  be  networked
26       respectively.
27
28       If  the  file `/usr/spool/notes/.utilities/access-template' is present,
29       it contains a list of access-rights which  are  added  to  the  created
30       notesfile.   The  file contains lines of access-rights similar to those
31       used in the nfaccess(8) command.  In environments with dynamic creation
32       of notesfiles, such as on USENET nodes, one or more users can automati‐
33       cally be made directors of all new notesfiles.   If  appropriate,  they
34       can  be  removed  from  the  access list of newly created notesfiles as
35       needed.
36
37       Rmnf asks for verification of each notesfile before deleting  it.   The
38       notesfile  is  deleted  if  the  response  line  begins with a `y'.  If
39       invoked with the -f option, rmnf does not ask for  verification  before
40       deleting the notesfiles.
41
42       Only the notesfile owner is allowed to run mknf and rmnf.
43

BUGS

45       Rmnf  doesn't  understand  about absolute pathnames for notesfiles.  It
46       refuses to remove notesfiles specified by absolute pathnames.
47
48       Any user should be allowed to create private notesfiles in  directories
49       where he has permission.
50

FILES

52       /usr/spool/notes/.utilities             where these programs live.
53       /usr/spool/notes/.utilities/access-template
54                                               Default access-list.
55       /usr/spool/notes                        Default notesfile directory.
56

SEE ALSO

58       nfaccess(8), nfxmit(8), notes(1),
59       The Notesfile Reference Manual
60

AUTHORS

62       Ray Essick (uiucdcs!essick, essick%uiuc@csnet-relay.arpa)
63       Department of Computer Science
64       University of Illinois at Urbana-Champaign
65       Urbana, IL
66
67       Rob Kolstad (kolstad@convex.UUCP)
68       CONVEX Computer Corporation
69       Richardson, TX
70
71
72
73                            University of Illinois                     MKNF(8)
Impressum