Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

nfabort(3) [bsd man page]

NFABORT(3)						     Library Functions Manual							NFABORT(3)

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, Department of Computer Science University of Illinois at Urbana-Champaign Urbana, IL University of Illinois NFABORT(3)

Check Out this Related Man Page

CHECKNOTES(1)						      General Commands Manual						     CHECKNOTES(1)

checknotes - check for new notesfile articles SYNOPSIS
checknotes [ -qnvs ] [ -aname ] DESCRIPTION
Checknotes reports on the existence of new notes. The NFSEQ environment variable is read to determine the notesfiles to examine for new text. Checknotes then looks at each of the notesfiles to determine if there are new notes. The various flags specify the method of noti- fication. The flags are mutually exlusive. The -q option specifies a message ``There are new notes'' when such is the case. No text is printed if there are no new notes. Specify -n to get a message ``There are no new notes'' if this is the case. If there are new notes, no message is printed. With the -v option enabled, checknotes prints the name of each notesfile containing new notes. The -s option is silent; no output is produced. Regardless of the option, the program exits with 0 (TRUE) if new notes exist and with 1 (FALSE) if no new notes exist. The -a option specifies a subsequencer. This allows several people sharing the same signon to maintain their own sequencer files. This switch does not allow users to forge other user's sequencer files. Since the name is concatenated with the user name, arbitrarily long subsequencer names aren't necessarily unique. A good rule of thumb is to ensure the first 6 characters of any given user's subsequencer names are unique. FILES
/etc/passwd for the users name /etc/group for the users group(s) /usr/spool/notes the default notesfile data base /usr/spool/notes/.sequencer/user Sequencing timestamps for user. /usr/spool/notes/.sequencer/user:subsequencer Sub-sequencing timestamps for user. SEE ALSO
notes(1), The Notesfile Reference Manual AUTHORS
Ray Essick (uiucdcs!essick, 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 CHECKNOTES(1)
Man Page