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

FreeBSD Manual Pages

  
 
  

home | help
gss_verify_mic(3), gss_verify(3)
Check a MIC against a message; verify integrity of a received message
hpropd(8)
receive a propagated database
ibv_create_rwq_ind_table(3), ibv_destroy_rwq_ind_table (3)
create or destroy a Receive Work Queue Indirection Table (RWQ IND TBL)
ibv_create_srq(3), ibv_destroy_srq(3)
create or destroy a shared receive queue (SRQ)
ibv_create_srq_ex(3), ibv_destroy_srq(3)
create or destroy a shared receive queue (SRQ)
ibv_get_srq_num(3), ibv_get_srq_num (3)
return srq number associated with the given shared receive queue (SRQ)
ibv_modify_srq(3)
modify attributes of a shared receive queue (SRQ)
ibv_post_recv(3)
post a list of work requests (WRs) to a receive queue
ibv_post_srq_recv(3)
post a list of work requests (WRs) to a shared receive queue (SRQ)
ibv_query_srq(3)
get the attributes of a shared receive queue (SRQ)
ibv_srq_pingpong(1)
simple InfiniBand shared receive queue test
iflibtxrx(9)
Device Dependent Transmit and Receive Functions
kfd(8)
receive forwarded tickets
mail(1), Mail(1), mailx(1)
send and receive mail
mq_receive(2), mq_timedreceive(2)
receive a message from message queue (REALTIME)
msgrcv(2)
receive a message from a message queue
rdma_create_srq(3)
Allocate a shared receive queue
rdma_get_recv_comp(3)
retrieves a completed receive request
rdma_post_recv(3)
post a work request to receive an incoming message
rdma_post_recvv(3)
post a work request to receive incoming messages
recv(2), recvfrom(2), recvmsg(2), recvmmsg(2)
receive message(s) from a socket
rmail(8)
handle remote mail received via uucp
sctp_generic_recvmsg(2)
receive data from a peer
sctp_recvmsg(3)
receive a message from an SCTP socket
shutdown(2)
disable sends and/or receives on a socket
smbmsg(8)
send or receive messages over an SMBus
snmp_client(3), snmp_client_init(3), snmp_client_set_host(3), snmp_client_set_port(3), snmp_send_cb_f(3), snmp_timeout_cb_f(3), snmp_timeout_start_f(3), snmp_timeout_stop_f(3), snmp_open(3), snmp_close(3), snmp_pdu_create(3), snmp_add_binding(3), snmp_pdu_check(3), snmp_pdu_send(3), snmp_oid_append(3), snmp_parse_server(3), snmp_receive(3), snmp_table_cb_f(3), snmp_table_fetch(3), snmp_table_fetch_async(3), snmp_dialog(3), snmp_discover_engine(3)
SNMP client library
uart(4)
driver for Universal Asynchronous Receiver/Transmitter (UART) devices
zfs-receive(8)
Creates a snapshot whose contents are as specified in the stream provided on standard input
SSL_get0_peer_scts(3)
get SCTs received
822received(1)
print the Received fields in a mail message
CURLINFO_RTSP_CSEQ_RECV(3)
get the recently received CSeq
CURLINFO_STARTTRANSFER_TIME(3)
get the time until the first byte is received
CURLINFO_STARTTRANSFER_TIME_T(3)
get the time until the first byte is received
CURLMOPT_TIMERFUNCTION(3)
set callback to receive timeout values
CURLOPT_BUFFERSIZE(3)
set preferred receive buffer size
CURLOPT_HEADERFUNCTION(3)
callback that receives header data
CURLOPT_WRITEFUNCTION(3)
set callback for writing received data
HPL_recv(3)
Receive a message
HPL_sdrv(3)
Send and receive a message
MPE_Log_comm_receive(4)
log the receive event of a message within a specified MPI_Comm (on the calling thread where receive event takes place)
MPE_Log_receive(4)
log the receive event of a message within MPI_COMM_WORLD. (on the calling thread where send event takes place)
MPIX_Comm_reenable_anysource(3)
Re-enable the ability to post receives using MPI_ANY_SOURCE on the communicator
MPIX_Imrecv(3)
Nonblocking receive of message matched by MPIX_Mprobe or MPIX_Improbe
MPIX_Mrecv(3)
Blocking receive of message matched by MPIX_Mprobe or MPIX_Improbe
MPIX_Neighbor_allgather(3)
In this function, each process i gathers data items from each process j if an edge (j,i) exists in the topology graph, and each process i sends the same data items to all processes j where an edge (i,j) exists. The send buffer is sent to each neighboring process and the l-th block in the receive buffer is received from the l-th neighbor
MPIX_Neighbor_alltoall(3)
In this function, each process i receives data items from each process j if an edge (j,i) exists in the topology graph or Cartesian topology. Similarly, each process i sends data items to all processes j where an edge (i,j) exists. This call is more general than MPI_NEIGHBOR_ALLGATHER in that different data items can be sent to each neighbor. The k-th block in send buffer is sent to the k-th neighboring process and the l-th block in the receive buffer is received from the l-th neighbor
MPIX_Neighbor_alltoallw(3)
Like MPIX_Neighbor_alltoallv but it allows one to send and receive with different types to and from each neighbor
MPI_Imrecv(3)
Nonblocking receive of message matched by MPI_Mprobe or MPI_Improbe
MPI_Irecv(3)
Begins a nonblocking receive
MPI_Mrecv(3)
Blocking receive of message matched by MPI_Mprobe or MPI_Improbe
MPI_Neighbor_allgather(3)
In this function, each process i gathers data items from each process j if an edge (j,i) exists in the topology graph, and each process i sends the same data items to all processes j where an edge (i,j) exists. The send buffer is sent to each neighboring process and the l-th block in the receive buffer is received from the l-th neighbor
MPI_Neighbor_alltoall(3)
In this function, each process i receives data items from each process j if an edge (j,i) exists in the topology graph or Cartesian topology. Similarly, each process i sends data items to all processes j where an edge (i,j) exists. This call is more general than MPI_NEIGHBOR_ALLGATHER in that different data items can be sent to each neighbor. The k-th block in send buffer is sent to the k-th neighboring process and the l-th block in the receive buffer is received from the l-th neighbor
MPI_Neighbor_alltoallw(3)
Like MPI_Neighbor_alltoallv but it allows one to send and receive with different types to and from each neighbor
MPI_Recv(3)
Blocking receive for a message
MPI_Recv_init(3)
Create a persistent request for a receive
MPI_Sendrecv(3)
Sends and receives a message
MPI_Sendrecv_replace(3)
Sends and receives using a single buffer
NetSNMP::TrapReceiver(3)
Embedded perl trap handling for Net-SNMP's snmptrapd
SP_receive(3), SP_scat_receive(3)
Receive message from Spread
SSL_get0_peer_scts(3)
get SCTs received
XkbNoteControlsChanges(3)
Notes the changes in a changes structure when a client receives an XkbControlsNotify event
XmImSetFocusValues(3)
An input manager function that notifies an input manager that a widget has received input focus and updates the input context attributes "XmImSetFocusValues" "input manager functions" "XmImSetFocusValues"
XmImVaSetFocusValues(3)
An input manager function that notifies an input manager that a widget has received input focus and updates the input context attributes "XmImVaSetFocusValues" "input manager functions" "XmImVaSetFocusValues"
XmProcessTraversal(3)
A function that determines which component receives keyboard events when a widget has the focus "XmProcessTraversal"
XmSetProtocolHooks(3)
A VendorShell function that allows preactions and postactions to be executed when a protocol message is received from MWM "XmSetProtocolHooks" "VendorShell functions" "XmSetProtocolHooks" "protocols"
XmSetWMProtocolHooks(3)
A VendorShell convenience interface that allows preactions and postactions to be executed when a protocol message is received from the window manager "XmSetWMProtocolHooks" "VendorShell functions" "XmSetWMProtocolHooks" "protocols"
XmtSetInitialFocus(3), XmtSetInitialFocus()(3)
set the widget to receive the initial keyboard focus in a dialog
a800(4)
webcamd driver for AVerMedia AverTV A800 DVB-T receiver
adintool(1)
a tool to record / split / send / receive audio streams
aepatch(1)
send and receive changes as patches
aerevml(1)
send and receive RevML change sets
af9005(4)
webcamd driver for Afatech 9005 DVB-T receiver
af9015(4)
webcamd driver for Afatech 9015 DVB-T receiver
aird(1)
USB Apple IR receiver daemon
aseqdump(1)
show the events received at an ALSA sequencer port
boobmsg(1)
send and receive message threads
brecv(3)
receives data from a bytestream socket
brecvl(3)
receives data from a bytestream socket
checkmail(1)
plays a sound file when the user receives mail
chrecv(3)
receives a message from a channel
coap_io(3), coap_run_once(3), coap_context_get_coap_fd(3)
Work with CoAP I/O to do the packet send and receives
ctm_smail(8), ctm_dequeue(8), ctm_rmail(8)
send and receive ctm(8) deltas via mail
cups-lpd(8)
receive print jobs and report printer status to lpd clients (deprecated)
curl_easy_recv(3)
receives raw data on an "easy" connection
dbmail-lmtpd(8)
receive messages from an MTA supporting the Lightweight Mail Transport Protocol, as specified in RFC 2033
dcmpsrcv(1)
Network receive for presentation state viewer
dcmrecv(1)
Simple DICOM storage SCP (receiver)
dvconnect(1)
receive or transmit raw DV using the video1394 device
efax(1)
send/receive faxes with Class 1, 2 or 2.0 fax modem (Please read the fax man page first.)
faxabort(8c)
tell a server to abort a receive
faxinfo(8c)
print information about a received facsimile
faxrcvd(8c)
notification script for received facsimile
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
fi_msg(3)
Message data transfer operations fi_recv / fi_recvv / fi_recvmsg Post a buffer to receive an incoming message fi_send / fi_sendv / fi_sendmsg fi_inject / fi_senddata : Initiate an operation to send a message
fi_tagged(3)
Tagged data transfer operations fi_trecv / fi_trecvv / fi_trecvmsg Post a buffer to receive an incoming message fi_tsend / fi_tsendv / fi_tsendmsg / fi_tinject / fi_tsenddata Initiate an operation to send a message
flow-receive(1)
Receive flow data with the NetFlow protocol
fstrm_capture(1)
Receive and save Frame Streams data from a socket
gammu-smsd-run(7)
documentation for RunOnReceive directive rst2man-indent-level 0 1 rstReportMargin \$1
git-fetch-pack(1)
Receive missing objects from another repository
git-receive-pack(1)
Receive what is pushed into the repository
gpsd(8)
interface daemon for GPS receivers
hpropd(8)
receive a propagated database
http_recvfield(3)
receives HTTP field from the peer
http_recvrequest(3)
receives HTTP request from the peer
http_recvstatus(3)
receives HTTP status from the peer
huh(1)
redisplay last telegram received
im_tcp(8), tcp input module(8)
syslogd(8) input module used to receive from tcp connections
kfd(8)
receive forwarded tickets
knet_handle_enable_pmtud_notify(3)
install a callback to receive PMTUd changes
knet_handle_enable_sock_notify(3)
Register a callback to receive socket events
knet_recv(3)
Receive data from knet nodes
libowfat_io_receivefd(3), io_receivefd(3)
receive a file descriptor over a Unix Domain socket
libowfat_socket_recv4(3), socket_recv4(3)
receive a UDP datagram
libowfat_socket_recv6(3), socket_recv6(3)
receive a UDP datagram
libssh2_channel_receive_window_adjust(3)
adjust the channel window
libssh2_channel_receive_window_adjust2(3)
adjust the channel window
lightning-getinfo(7)
Command to receive all information about the c-lightning node
lrz(1), rx(1), rb(1), rz(1)
XMODEM, YMODEM, ZMODEM (Batch) file receive
lxi_receive(3)
receive message from LXI device
mailx(1)
send and receive Internet mail
minirsyslogd(8)
highly efficient, minimalistic, remote-only syslog receiver
modbus_receive(3)
receive an indication request
modbus_receive_confirmation(3)
receive a confirmation request
modbus_reply(3)
send a reponse to the received request
mrecv(3)
receives a message
mrecvl(3)
receives a message
mtr-packet(8)
send and receive network probes
mtrace(8)
print multicast path from a source to a receiver
netdumpd(8)
receive kernel core dumps over the network
newsmail(8cn), recenews(8cn), recpnews(8cn)
receive mailed news bdecode - decode encoded mailed news
nfc-dep-initiator(1)
Demonstration tool to send/received data as D.E.P. initiator
nfc-dep-target(1)
Demonstration tool to send/received data as D.E.P. target
nn_recv(3)
receive a message
pg_receivewal(1)
stream write-ahead logs from a PostgreSQL server
pg_receivexlog(1)
stream transaction logs from a PostgreSQL server
ping_iterator_get_info(3)
Receive information about a host
pollrcvd(8c)
script for delivering facsimile received by polling
pvm_gather(3)
A specified member of the group receives messages from each member of the group and gathers these messages into a single array
pvm_getrbuf(3)
Returns the message buffer identifier for the active receive buffer
pvm_nrecv(3)
Non-blocking receive
pvm_precv(3)
Receive a message directly into a buffer
pvm_recv(3)
Receive a message
pvm_setrbuf(3)
Switches the active receive buffer and saves the previous buffer
pvm_trecv(3)
Receive with timeout
qboobmsg(1)
send and receive message threads
rcvdist(1)
asynchronously receive and distribute new email
recvq(5f), recvq/fax*(5f)
received facsimile document format
recvstats(8c)
summarize receive accounting information
rigctl(1)
control radio transceivers and receivers
rigmem(1)
backup and restore memory of radio transceivers and receivers
rmail(8)
handle remote mail received via uucp
roadmap(1)
Street navigation system using vector maps and a GPS receiver
rwreceiver(8)
Accepts files transferred from rwsender(s)
rwsender(8)
Watch directory for files and transfer them to rwreceiver(s)
s-nail(1), %[](1)
send and receive Internet mail
sc_BcastStateRecv(3), sc::BcastStateRecv(3)
BcastStateRecv does the receive part of a broadcast of an object to all nodes
sc_MsgStateRecv(3), sc::MsgStateRecv(3)
The MsgStateRecv is an abstract base class that receives objects from nodes in a MessageGrp
sc_StateRecv(3), sc::StateRecv(3)
StateRecv is a concrete specialization of MsgStateRecv that does the receive part of point to point communication in a MessageGrp
sc_intMessageGrp(3), sc::intMessageGrp(3)
Uses integer message types to send and receive messages
showpicture(1)
View an image received in the mail
snmptrapd(8)
Receive and log SNMP trap messages
snmptrapd.conf(5)
configuration file for the Net-SNMP notification receiver
udp_recv(3)
receives an UDP packet
udp_recvl(3)
receives an UDP packet
udpdump(1)
Provide an UDP receiver that gets packets from network devices (like Aruba routers) and exports them in PCAP format
ws_recv(3)
receives a WebSocket message
ws_recvl(3)
receives a WebSocket message
xs_recv(3)
receive a message part from a socket
xs_recvmsg(3)
receive a message part from a socket (zero-copy)
zfs-receive(8)
Creates a snapshot whose contents are as specified in the stream provided on standard input
zmq_msg_more(3)
indicate if there are more message parts to receive
zmq_msg_recv(3)
receive a message part from a socket
zmq_recv(3)
receive a message part from a socket
zmq_recvmsg(3)
receive a message part from a socket
AnyEvent::Twitter::Stream(3)
Receive Twitter streaming API in an event loop
Brackup::Dict::Null(3)
noop key-value dictionary implementation, discarding everything it receives
Frontier::Daemon(3)
receive Frontier XML RPC requests
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
GraphQL::Language::Receiver(3)
GraphQL Pegex AST constructor
IO::Socket::Multicast(3)
Send and receive multicast messages
IO::Socket::Multicast6(3)
Send and receive IPv4 and IPv6 multicast messages
MPI_Alltoallv(3), MPI_Ialltoallv(3)
All processes send different amount of data to, and receive different amount of data from, all processes
MPI_Alltoallw(3), MPI_Ialltoallw(3)
All processes send data of different types to, and receive data of different types from, all processes
MPI_Get_count(3), MPI_Get_count (3)
Gets the number of top-level elements received
MPI_Imrecv(3)
Non-blocking receive for a matched message
MPI_Irecv(3)
Starts a standard-mode, nonblocking receive
MPI_Mrecv(3)
Blocking receive for a matched message
MPI_Neighbor_alltoallv(3), MPI_Ineighbor_alltoallv(3)
All processes send different amounts of data to, and receive different amounts of data from, all neighbors
MPI_Neighbor_alltoallw(3), MPI_Ineighbor_alltoallw(3)
All processes send data of different types to, and receive data of different types from, all processes
MPI_Recv(3)
Performs a standard-mode blocking receive
MPI_Recv_init(3)
Builds a handle for a receive
MPI_Sendrecv(3)
Sends and receives a message
MPI_Sendrecv_replace(3)
Sends and receives a message using a single buffer
MPI_Test(3)
Tests for the completion of a specific send or receive
MPI_Wait(3)
Waits for an MPI send or receive to complete
MPI_Waitany(3)
Waits for any specified send or receive to complete
Mail::DMARC::Report::Receive(3)
process incoming DMARC reports
Mail::Field::Received(3)
-- mostly RFC822-compliant parser of Received headers
Mail::Transport::POP3(3)
receive messages via POP3
Mail::Transport::Receive(3)
receive messages
Net::Analysis::Listener::Example1(3)
emit/receive custom events
Net::Packet(3)
a framework to easily send and receive frames from layer 2 to layer 7
Net::RTP(3)
Send and receive RTP packets (RFC3550)
Net::SIP::ReceiveChain(3)
handle incoming packet by multiple receivers
POE::Stage::Receiver(3)
a simple UDP recv/send component
Paws::SQS::ReceiveMessage(3)
Arguments for method ReceiveMessage on Paws::SQS
Pegex::Receiver(3)
Base Class for All Pegex Receivers
Pegex::Tree(3)
Pegex Parse Tree Receiver
Pegex::Tree::Wrap(3)
Pegex Wrapper Parse Tree Receiver
Reflex::Signal(3)
receive callbacks when signals arrive
SVN::Notify::Filter::AuthZMail(3)
Determines Subversion accounts to receive the email, via the AuthZSVNAccess file
SyslogScan::Summary(3)
-- encapsulates a tally of how many bytes people have sent and received through sendmail
SyslogScan::Usage(3)
-- encapsulates the total volumes of mail broadcast, sent, and received through sendmail by a single user or group. SyslogScan::Volume -- encapsulates a number of messages along with a total number of bytes
Tk::DropSite(3)
Receive side of Drag & Drop abstraction
WWW::OpenSearch::Response(3)
Encapsulate a response received from an A9 OpenSearch compatible engine
bk-receive(1), bk receive(1)
receive a patch
dmarc_receive(1)
receive aggregate reports via IMAP, mbox, or message file(s)
mailx(1)
send and receive mail
midicat(1)
send to or receive from MIDI ports
r2e(1)
receive RSS feeds by email
snmpa_notification_delivery_info_receiver(3)
Behaviour module for the SNMP agent notification delivery information receiver
trap(1)
perform an action when the shell receives a signal rst2man-indent-level 0 1 rstReportMargin \$1
home | help