nfabort(3) [bsd man page]
NFABORT(3) Library Functions Manual NFABORT(3) NAME
nfabort - dump core and log it in a notesfile SYNOPSIS
nfabort ( notesfile, message, title, cname, exitcode ) char *notesfile, *message, *title, *cname, exitcode cc ... -lnfcom DESCRIPTION
Nfabort provides user programs with a convenient way to generate a core image, move it to a save place, and log the action in a notesfile. The notesfile parameter specifies the notesfile to receive a copy of the string message with a line appended detailing the final resting place of the core image. The text is inserted into the notesfile as a base note with title taken from the parameter list. Cname is the prefix of the pathname of where to place the core image. This is suffixed with ``.integer'' to yield the full pathname. The integer is generated from the pid of the current process. After generating and saving the core image and placing the message in the notesfile, nfabort terminates the current process with the exit code specified by the exitcode parameter. Nfabort calls nfcomment to insert the message into the notesfile. BUGS
Certain conditions, such as running out of memory, will cause nfabort to fail. Nfabort will fail to log the message if it can't fork a child process. The final resting place of the core image will not be logged if nfabort can't allocate memory for temporary strings. FILES
/usr/lib/libnfcom.a -lnfcom library SEE ALSO
malloc(3), nfcomment(3), nfpipe(1), notes(1), popen(3S), system(3), 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 University of Illinois NFABORT(3)
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)