pfm_inhibit_faults(3ncs)pfm_inhibit_faults(3ncs)Name
pfm_inhibit_faults - inhibit asynchronous faults
Syntax
#include <idl/c/base.h>
#include <idl/c/pfm.h>
void pfm_$inhibit_faults()
Description
The routine prevents asynchronous faults from being passed to the calling process. While faults are inhibited, the operating system holds
at most one asynchronous fault. Consequently, a call to can result in the loss of some signals. It is good practice to inhibit faults
only when absolutely necessary. This call has no effect on the processing of synchronous faults such as floating-point and overflow excep-
tions, access violations, and so on.
FilesSee Alsointro(3ncs), pfm_enable_faults(3ncs), pfm_inhibit(3ncs)pfm_inhibit_faults(3ncs)
Check Out this Related Man Page
pfm_rls_cleanup(3ncs)pfm_rls_cleanup(3ncs)Name
pfm_rls_cleanup - release clean-up handlers
Syntax
#include <idl/c/base.h>
#include <idl/c/pfm.h>
void pfm_$rls_cleanup(cleanup_record, status)
pfm_$cleanup_rec *cleanup_record;
status_$t *status;
Arguments
cleanup_record The clean-up record for the first clean-up handler to release.
status The completion status. If status is pfm_$bad_rls_order, it means that the caller attempted to release a clean-up han-
dler before releasing all handlers established after it. This status is only a warning; the intended clean-up handler
is released, along with all clean-up handlers established after it. If the completion status returned in is equal to
status_$ok, then the routine that supplied it was successful.
Description
The routine releases the clean-up handler associated with cleanup_record and all clean-up handlers established after it.
Diagnostics
This section lists the status codes for errors returned by this routine in
pfm_$bad_rls_order Attempted to release a clean-up handler out of order.
pfm_$cleanup_not_found
There is no pending clean-up handler.
pfm_$cleanup_set A clean-up handler was established successfully.
pfm_$cleanup_set_signalled
Attempted to use pfm_$cleanup_set as a signal.
pfm_$invalid_cleanup_rec
Passed an invalid clean-up record to a routine.
FilesSee Alsointro(3ncs)pfm_rls_cleanup(3ncs)
<h1>A short history of UNIX</h1>
<p>In the late 1960's Ken Thompsom joined the computing-science research group at Bell
Laboratories, which is the research arm of the giant American corporation ATT. He and many
colleagues had been collaborating with MIT and GE on the development of an... (0 Replies)
We have quite a few threads about this subject. I have collected some of them and arranged them by the OS which is primarily discussed in the thread. That is because the exact procedure depends on the OS involved. What's more, since you often need to interact with the boot process, the... (0 Replies)
I'm writing a command shell, and I want to be able to detect when the user presses an arrow key (otherwise it just prints [[A, [[B, etc.). I know it's relatively easy (although somewhat more time-consuming) to detect keystrokes in noncanonical mode, but I've noticed that the bash shell detects... (4 Replies)
I'm learning off Linux (Ubuntu) right now. I want to move up to Unix, but I don't want to rush like I did when it came to Windows --> to Linux. What is the best Unix OS that fits in pretty well with Ubuntu.
In other words is there kind of an equal Linux with Unix?
Also what do I need to... (10 Replies)
I noticed my hostname is <my-full-name>s-macbook.local. I'm not sure exactly what information leaves the local network, and whether the hostname is included, but if it is, this would mean people on the Internet can look at my hostname and see who I am. Before anyone says that's not possible,... (4 Replies)