nfrcv(8) [bsd man page]

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

NAME

       nfxmit, nfrcv - notesfile networking programs

SYNOPSIS

       nfxmit -dsite [ -r ] [ -a ] [ -i ] [ -t date-spec ] [ -f file ] topic [ ... ]

       nfrcv topic fromsystem

DESCRIPTION

       Nfxmit  and nfrcv implement networking of notesfiles.  The nfxmit program packages eligible new articles and sends them to a remote system.
       Nfrcv is the receiving end of this team.

       Nfxmit sends the specified notesfiles to the site specified with the -d option.	The -r option specifies that a request	should	be  queued
       for  the  remote  site  to  transmit updates from its copies of the notesfiles sent.  The -r option is used only if the other site does not
       automatically queue updates of the notesfile.

       Specify -a to have articles which originated in news(1) sent.  News(1)-originated articles will usually reach each system via the news pro-
       gram.

       The  -i option indicates that nfxmit is to send articles to the destination that it normally would not send.  These articles are those that
       were written there or were received at the local site from that particular site.  The -i option is separate from the  timestamp	functions.
       Articles  are  first  selected  on the basis of the time received and criteria for having passed through news or the destination system are
       applied later.

       A timestamp of the last transmission of each notesfile to each system is maintained. This is used for determining the notes to send.  If  a
       different timestamp is desired, use the -t option.  The supplied timestamp is used for this transfer and the stored timestamp is updated.

       Specify	-f  myfile  on	the  command line to have nfxmit read myfile for a list of notesfiles to be sent.  This is useful if the number of
       notesfiles is too numerous to list on a single command line.  The shell meta-characters *, ?, [, and ] are recognized  in  both	the  topic
       parameter and the entries in myfile.

       Nfxmit  uses  uux(I)  to  invoke nfrcv on the remote system in order to process the incoming notes.  Non-uucp connections are supported and
       specified in the file /usr/spool/notes/.utilities/net.how

FILES

       /usr/spool/notes/.utilities/net.how	    specifies connection methods between systems
       /usr/spool/notes/.utilities/net.alias	    directory containing mapping of local and remote notesfile names
       /usr/spool/notes/.sequencer/Sy:sysname	    Seqeuncing timestamps for sysname.

SEE ALSO

       news(1), notes(1), nfcomment(3), uucp(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							 NFXMIT(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)

Linux and UNIX Man Pages

nfrcv(8) [bsd man page]

Check Out this Related Man Page