Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
callout_active(9), callout_deactivate(9), callout_async_drain(9), callout_drain(9), callout_handle_init(9), callout_init(9), callout_init_mtx(9), callout_init_rm(9), callout_init_rw(9), callout_pending(9), callout_reset(9), callout_reset_curcpu(9), callout_reset_on(9), callout_reset_sbt(9), callout_reset_sbt_curcpu(9), callout_reset_sbt_on(9), callout_schedule(9), callout_schedule_curcpu(9), callout_schedule_on(9), callout_schedule_sbt(9), callout_schedule_sbt_curcpu(9), callout_schedule_sbt_on(9), callout_stop(9), callout_when(9), timeout(9), untimeout(9)
execute a function after a specified length of time
pci(9), pci_alloc_msi(9), pci_alloc_msix(9), pci_disable_busmaster(9), pci_disable_io(9), pci_enable_busmaster(9), pci_enable_io(9), pci_find_bsf(9), pci_find_cap(9), pci_find_dbsf(9), pci_find_device(9), pci_find_extcap(9), pci_find_htcap(9), pci_find_next_cap(9), pci_find_next_extcap(9), pci_find_next_htcap(9), pci_find_pcie_root_port(9), pci_get_id(9), pci_get_max_payload(9), pci_get_max_read_req(9), pci_get_powerstate(9), pci_get_vpd_ident(9), pci_get_vpd_readonly(9), pci_iov_attach(9), pci_iov_attach_name(9), pci_iov_detach(9), pci_msi_count(9), pci_msix_count(9), pci_msix_pba_bar(9), pci_msix_table_bar(9), pci_pending_msix(9), pci_read_config(9), pci_release_msi(9), pci_remap_msix(9), pci_restore_state(9), pci_save_state(9), pci_set_max_read_req(9), pci_set_powerstate(9), pci_write_config(9), pcie_adjust_config(9), pcie_flr(9), pcie_get_max_completion_timeout(9), pcie_read_config(9), pcie_wait_for_pending_transactions(9), pcie_write_config(9)
PCI bus interface
rdma_get_cm_event(3)
Retrieves the next pending communication event
rdma_get_request(3)
Retrieves the next pending connection request event
signal(9), SIGADDSET(9), SIGDELSET(9), SETEMPTYSET(9), SIGFILLSET(9), SIGISMEMBER(9), SIGISEMPTY(9), SIGNOTEMPTY(9), SIGSETEQ(9), SIGSETNEQ(9), SIGSETOR(9), SIGSETAND(9), SIGSETNAND(9), SIGSETCANTMASK(9), SIG_STOPSIGMASK(9), SIG_CONTSIGMASK(9), SIGPENDING(9), cursig(9), execsigs(9), issignal(9), killproc(9), pgsigio(9), postsig(9), sigexit(9), siginit(9), signotify(9), trapsignal(9)
kernel signal functions
sigpending(2)
get pending signals
sync(8)
force completion of pending disk writes (flush cache)
usb_fifo_alloc_buffer(9), usb_fifo_attach(9), usb_fifo_detach(9), usb_fifo_free_buffer(9), usb_fifo_get_data(9), usb_fifo_get_data_buffer(9), usb_fifo_get_data_error(9), usb_fifo_get_data_linear(9), usb_fifo_put_bytes_max(9), usb_fifo_put_data(9), usb_fifo_put_data_buffer(9), usb_fifo_put_data_error(9), usb_fifo_put_data_linear(9), usb_fifo_reset(9), usb_fifo_softc(9), usb_fifo_wakeup(9), usbd_do_request(9), usbd_do_request_flags(9), usbd_errstr(9), usbd_lookup_id_by_info(9), usbd_lookup_id_by_uaa(9), usbd_transfer_clear_stall(9), usbd_transfer_drain(9), usbd_transfer_pending(9), usbd_transfer_poll(9), usbd_transfer_setup(9), usbd_transfer_start(9), usbd_transfer_stop(9), usbd_transfer_submit(9), usbd_transfer_unsetup(9), usbd_xfer_clr_flag(9), usbd_xfer_frame_data(9), usbd_xfer_frame_len(9), usbd_xfer_get_frame(9), usbd_xfer_get_priv(9), usbd_xfer_is_stalled(9), usbd_xfer_max_framelen(9), usbd_xfer_max_frames(9), usbd_xfer_max_len(9), usbd_xfer_set_flag(9), usbd_xfer_set_frame_data(9), usbd_xfer_set_frame_len(9), usbd_xfer_set_frame_offset(9), usbd_xfer_set_frames(9), usbd_xfer_set_interval(9), usbd_xfer_set_priv(9), usbd_xfer_set_stall(9), usbd_xfer_set_timeout(9), usbd_xfer_softc(9), usbd_xfer_state(9), usbd_xfer_status(9)
Universal Serial Bus driver programming interface
BIO_ctrl(3), BIO_callback_ctrl(3), BIO_ptr_ctrl(3), BIO_int_ctrl(3), BIO_reset(3), BIO_seek(3), BIO_tell(3), BIO_flush(3), BIO_eof(3), BIO_set_close(3), BIO_get_close(3), BIO_pending(3), BIO_wpending(3), BIO_ctrl_pending(3), BIO_ctrl_wpending(3), BIO_get_info_callback(3), BIO_set_info_callback(3), BIO_info_cb(3)
BIO control operations
SSL_get_current_cipher(3), SSL_get_cipher_name(3), SSL_get_cipher(3), SSL_get_cipher_bits(3), SSL_get_cipher_version(3), SSL_get_pending_cipher(3)
get SSL_CIPHER of a connection
SSL_key_update(3), SSL_get_key_update_type(3), SSL_renegotiate(3), SSL_renegotiate_abbreviated(3), SSL_renegotiate_pending(3)
initiate and obtain information about updating connection keys
SSL_pending(3), SSL_has_pending(3)
check for readable bytes buffered in an SSL object
ASDatabase(1x)
defines how windows should be treated by AfterStep depending on its name
BIO_ctrl(3), BIO_callback_ctrl(3), BIO_ptr_ctrl(3), BIO_int_ctrl(3), BIO_reset(3), BIO_seek(3), BIO_tell(3), BIO_flush(3), BIO_eof(3), BIO_set_close(3), BIO_get_close(3), BIO_pending(3), BIO_wpending(3), BIO_ctrl_pending(3), BIO_ctrl_wpending(3), BIO_get_info_callback(3), BIO_set_info_callback(3), BIO_info_cb(3), BIO_get_ktls_send(3), BIO_get_ktls_recv(3)
BIO control operations
CURLOPT_APPEND(3)
enable appending to the remote file
SDL_PollEvent(3)
Polls for currently pending events
SSL_get_current_cipher(3), SSL_get_cipher_name(3), SSL_get_cipher(3), SSL_get_cipher_bits(3), SSL_get_cipher_version(3), SSL_get_pending_cipher(3)
get SSL_CIPHER of a connection
SSL_key_update(3), SSL_get_key_update_type(3), SSL_renegotiate(3), SSL_renegotiate_abbreviated(3), SSL_renegotiate_pending(3)
initiate and obtain information about updating connection keys
SSL_pending(3), SSL_has_pending(3)
check for readable bytes buffered in an SSL object
TIFFFlush(3tiff), TIFFFlushData(3tiff)
flush pending writes to an open TIFF file
Tcl_CancelIdleCall.tcl85(3), Tcl_DoWhenIdle(3), Tcl_CancelIdleCall(3)
invoke a procedure when there are no pending events
Tcl_CancelIdleCall.tcl86(3), Tcl_DoWhenIdle(3), Tcl_CancelIdleCall(3)
invoke a procedure when there are no pending events
Tcl_CancelIdleCall.tcl87(3), Tcl_DoWhenIdle(3), Tcl_CancelIdleCall(3)
invoke a procedure when there are no pending events
XFlush(3), XSync(3), XEventsQueued(3), XPending(3)
handle output buffer or event queue
XmClipboardInquirePendingItems(3)
A clipboard function that returns a list of data ID/private ID pairs "XmClipboardInquirePending\%Items" "clipboard functions" "XmClipboardInquirePending\%Items"
XmUpdateDisplay(3)
A function that processes all pending exposure events immediately "XmUpdateDisplay"
XmtCliFlush(3), XmtCliFlush()(3)
force pending XmtCli output to be displayed
XmtDiscardButtonEvents(3), XmtDiscardButtonEvents()(3), XmtDiscardKeyPressEvents()(3)
discard pending user input events
XmtMenuActivateProcedure(3), XmtMenuActivateProcedure()(3), XmtMenuInactivateProcedure()(3)
sensitize and desensitize menu items depending on the procedures they call
XtAppNextEvent(3), XtAppPending(3), XtAppPeekEvent(3), XtAppProcessEvent(3), XtDispatchEvent(3), XtAppMainLoop(3)
query and process events and input
XtNextEvent(3), XtPending(3), XtPeekEvent(3), XtProcessEvent(3), XtMainLoop(3)
query and process events and input
case.tcl85(n), case(n)
Evaluate one of several scripts, depending on a given value
case.tcl86(n), case(n)
Evaluate one of several scripts, depending on a given value
case.tcl87(n), case(n)
Evaluate one of several scripts, depending on a given value
drmHandleEvent(3)
read and process pending DRM events
exexedat(3)
Appending datafiles onto your executable. Allegro game programming library
ezmlm-gate(1)
Gate posts depending on message SENDER
fi_endpoint(3)
Fabric endpoint operations fi_endpoint / fi_scalable_ep / fi_passive_ep / fi_close Allocate or close an endpoint. fi_ep_bind Associate an endpoint with hardware resources, such as event queues, completion queues, counters, address vectors, or shared transmit/receive contexts. fi_scalable_ep_bind Associate a scalable endpoint with an address vector fi_pep_bind Associate a passive endpoint with an event queue fi_enable Transitions an active endpoint into an enabled state. fi_cancel Cancel a pending asynchronous data transfer fi_ep_alias Create an alias to the endpoint fi_control Control endpoint operation. fi_getopt / fi_setopt Get or set endpoint options. fi_rx_context / fi_tx_context / fi_srx_context / fi_stx_context Open a transmit or receive context. fi_tc_dscp_set / fi_tc_dscp_get Convert between a DSCP value and a network traffic class fi_rx_size_left / fi_tx_size_left (DEPRECATED) Query the lower bound on how many RX/TX operations may be posted without an operation returning -FI_EAGAIN. This functions have been deprecated and will be removed in a future version of the library
git-request-pull(1)
Generates a summary of pending changes
gl_io_mode(3), gl_raw_io(3), gl_normal_io(3), gl_tty_signals(3), gl_abandon_line(3), gl_handle_signal(3), gl_pending_io(3)
How to use gl_get_line() from an external event loop
gnutls_record_check_pending(3)
API function
libowfat_io_appendfile(3), io_appendfile(3)
open a file for appending
libowfat_open_append(3), open_append(3)
open a file for appending
memcached_append(3)
Appending to or Prepending to data on the server rst2man-indent-level 0 1 rstReportMargin \$1
memcached_append_by_key(3)
Appending to or Prepending to data on the server rst2man-indent-level 0 1 rstReportMargin \$1
memcached_prepend(3)
Appending to or Prepending to data on the server rst2man-indent-level 0 1 rstReportMargin \$1
memcached_prepend_by_key(3)
Appending to or Prepending to data on the server rst2man-indent-level 0 1 rstReportMargin \$1
page_revoke(3), page_revokeRevocation methods(3)
There are two revocation method for PKIX/X.509: CRL and OCSP. Revocation is needed if the private key is lost and stolen. Depending on how picky you are, you might want to make revocation for destroyed private keys too (smartcard broken), but that should not be a problem. CRL is a list of certifiates that have expired. OCSP is an online checking method where the requestor sends a list of certificates to the OCSP server to return a signed reply if they are valid or not. Some services sends a OCSP reply as part of the hand-shake to make the revoktion decision simpler/faster for the client
qconfirm-accept(1)
confirms delivery of pending messages held by qconfirm-check
sc_BcastState(3), sc::BcastState(3)
This creates and forwards/retrieves data from either a BcastStateRecv or a BcastStateSend depending on the value of the argument to constructor
switch.tcl85(n), switch(n)
Evaluate one of several scripts, depending on a given value
switch.tcl86(n), switch(n)
Evaluate one of several scripts, depending on a given value
switch.tcl87(n), switch(n)
Evaluate one of several scripts, depending on a given value
update.tcl85(n), update(n)
Process pending events and idle callbacks
update.tcl86(n), update(n)
Process pending events and idle callbacks
update.tcl87(n), update(n)
Process pending events and idle callbacks
Algorithm::Evolutionary::Hash_Wheel(3)
Random selector of things depending on probabilities
Algorithm::Evolutionary::Op::Mutation(3)
BitFlip mutation, changes several bits in a bitstring, depending on the probability
Algorithm::Evolutionary::Wheel(3)
Random selector of things depending on probabilities
File::Append::TempFile(3)
Perl extension for appending data to files
Filter::Template::UseBytes(3)
conditionally use bytes.pm depending on availability
Gantry::Conf::FAQ(3)
Frequently Asked Questions regarding Gantry::Conf "Why should I use Gantry::Conf at all?" 4 Item "Why should I use Gantry::Conf at all?" There are many reasons why we feel Gantry::Conf is helpful both during development and after deployment. The next two entries should hopefully answer this question for you as they outline a few common scenarios programmers and system administrators often face. "How is Gantry::Conf helpful during development?" 4 Item "How is Gantry::Conf helpful during development?" "Easy separation of development configs from production configs" 4 Item "Easy separation of development configs from production configs" Often programmers have a separate development environment from their production environment. By using <shared> blocks and dev instances you can avoid spending any serious time setting up your application in the development environment. Take this configuration example: <shared dev> dbuser nobody dbpass secret dbconn "dbi:Pg:dbname=dev" </shared> <shared production> dbuser apache dbpass secret2 dbconn "dbi:Pg:dbname=production" </shared> <instance app1> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use production </instance> <instance app1-dev> ConfigureVia FlatFile Config::General /etc/apps/app1.conf use dev </instance> By separating out our production and dev database information into shared blocks we can essentially switch between our production and dev environments by simply changing the instance we are using. If you were working on a script this would be a simple matter of running: $ script.pl --instance=app1-dev instead of: $ script.pl --instance=app1 "How is Gatnry::Conf helpful in production?" 4 Item "How is Gatnry::Conf helpful in production?" Gantry::Conf has several advantages in a production environment. First, it provides a single place for all config information, if you commit to it. Even if you don't commit to it for all apps, it still provides control to the installing admin over how and where conf information is stored. For instance, the admin could put the config information directly into /etc/gantry.conf, or into a separate file in /etc/gantry.d. She could even set up a secure web server where all boxes would go to get their conf. The short answer is, Gantry::Conf is flexible and production environments benefit from flexibility. "How do I pass my instance information into my application?" 4 Item "How do I pass my instance information into my application?" There are many possible ways to do this a few of which are: "Command line arguments" 4 Item "Command line arguments" If your application accepts arguments on the command line we suggest adding an --instance option to pass in the instance's name. "PerlSetVar" 4 Item "PerlSetVar" In a mod_perl environment you could use a PerlSetVar, possibly named GantryConfInstance, to pull in this value for your application. "ModPerl::ParamBuilder" 4 Item "ModPerl::ParamBuilder" Again in a mod_perl environment, another option would be to use ModPerl::ParamBuilder to pass the instance name. "Hard coded" 4 Item "Hard coded" We include this for the sake of completeness, but advise against it. You could always simply hard code your instance information into your application, but this will greatly reduce the flexibility you have. "How do I add a different provider for an existing ConfigVia method?" 4 Item "How do I add a different provider for an existing ConfigVia method?" Place your provider module in the Gantry::Conf::Provider::Method::* namespace. Make sure your public API matches the existing providers which use the same method. For instance the flat file providers all implement a config method which is called as a class method and receives a file name. "How do I add to the ConfigVia methods?" 4 Item "How do I add to the ConfigVia methods?" If none of the existing provider methods will do, you need to work in Gantry::Conf. In particular, you need to augment the dispatch hash with the name of your provisioning method and a sub name which will handle it. Then you need to implement the method you put in %dispatch
Hash::Util::FieldHash::Compat(3)
Use Hash::Util::FieldHash or ties, depending on availability
Log::Log4perl::Appender::DBI(3)
implements appending to a DB
Net::DBus::Binding::PendingCall(3)
A handler for pending method replies
OpenXPKI::Crypto::Tool::SCEP::Command::create_pending_reply(3), Header(3)
"Name" OpenXPKI::Crypto::Tool::SCEP::Command::create_pending_reply
Paws::RDS::ApplyPendingMaintenanceAction(3)
Arguments for method ApplyPendingMaintenanceAction on Paws::RDS
Paws::RDS::DescribePendingMaintenanceActions(3)
Arguments for method DescribePendingMaintenanceActions on Paws::RDS
Paws::SimpleWorkflow::CountPendingActivityTasks(3)
Arguments for method CountPendingActivityTasks on Paws::SimpleWorkflow
Paws::SimpleWorkflow::CountPendingDecisionTasks(3)
Arguments for method CountPendingDecisionTasks on Paws::SimpleWorkflow
Signal::Pending(3)
Signal pending status made easy
VM::EC2::DB::PendingModifiedValues(3)
An RDS Database Pending Modifed Values object
Workflow::Condition(3)
Evaluate a condition depending on the workflow state and environment
bk-fixtool(1), bk fixtool(1)
fix up pending changes
bk-pending(1), bk pending(1)
list deltas which need to be in a changeset
find-updated(1)
-- generate a list of those ports depending on files that have been modified at a time different to the time stored in the cache
t(nged)
Lists the names of specified objects in the database in alphabetical order depending on the argument given
ttdt_Get_Modified(3)
ask if any ToolTalk client has changes pending on a file
unzipsfx(1)
self-extracting stub for prepending to ZIP archives
home | help