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

FreeBSD Manual Pages

  
 
  

home | help
accept(2), accept4(2)
accept a connection on a socket
accept_filter(9), accept_filt_add(9), accept_filt_del(9), accept_filt_generic_mod_event(9), accept_filt_get(9)
filter incoming connections
getstr(3), getnstr(3), wgetstr(3), wgetnstr(3), mvgetstr(3), mvgetnstr(3), mvwgetstr(3), mvwgetnstr(3)
accept character strings from curses terminal keyboard
gss_accept_sec_context(3)
Accept a security context initiated by a peer application
rdma_accept(3)
Called to accept a connection request
rpc_soc(3), auth_destroy(3), authnone_create(3), authunix_create(3), authunix_create_default(3), callrpc(3), clnt_broadcast(3), clnt_call(3), clnt_control(3), clnt_create(3), clnt_destroy(3), clnt_freeres(3), clnt_geterr(3), clnt_pcreateerror(3), clnt_perrno(3), clnt_perror(3), clnt_spcreateerror(3), clnt_sperrno(3), clnt_sperror(3), clntraw_create(3), clnttcp_create(3), clntudp_bufcreate(3), clntudp_create(3), clntunix_create(3), get_myaddress(3), pmap_getmaps(3), pmap_getport(3), pmap_rmtcall(3), pmap_set(3), pmap_unset(3), registerrpc(3), rpc_createerr(3), svc_destroy(3), svc_fds(3), svc_fdset(3), svc_getargs(3), svc_getcaller(3), svc_getreq(3), svc_getreqset(3), svc_register(3), svc_run(3), svc_sendreply(3), svc_unregister(3), svcerr_auth(3), svcerr_decode(3), svcerr_noproc(3), svcerr_noprog(3), svcerr_progvers(3), svcerr_systemerr(3), svcerr_weakauth(3), svcfd_create(3), svcunixfd_create(3), svcraw_create(3), svcunix_create(3), xdr_accepted_reply(3), xdr_authunix_parms(3), xdr_callhdr(3), xdr_callmsg(3), xdr_opaque_auth(3), xdr_pmap(3), xdr_pmaplist(3), xdr_rejected_reply(3), xdr_replymsg(3), xprt_register(3), xprt_unregister(3)
library routines for remote procedure calls
xdr_accepted_reply(3), xdr_authsys_parms(3), xdr_callhdr(3), xdr_callmsg(3), xdr_opaque_auth(3), xdr_rejected_reply(3), xdr_replymsg(3)
XDR library routines for remote procedure calls
zfs-jail(8)
Attaches and detaches ZFS filesystems from FreeBSD jails. A Tn ZFS dataset can be attached to a jail by using the Cm jail subcommand. You cannot attach a dataset to one jail and the children of the same dataset to another jail. You can also not attach the root file system of the jail or any dataset which needs to be mounted before the zfs rc script is run inside the jail, as it would be attached unmounted until it is mounted from the rc script inside the jail. To allow management of the dataset from within a jail, the jailed property has to be set and the jail needs access to the /dev/zfs device. The quota property cannot be changed from within a jail. See jail(8) for information on how to allow mounting ZFS datasets from within a jail. A Tn ZFS dataset can be detached from a jail using the Cm unjail subcommand. After a dataset is attached to a jail and the jailed property is set, a jailed file system cannot be mounted outside the jail, since the jail administrator might have set the mount point to an unacceptable value
BIO_s_accept(3), BIO_set_accept_name(3), BIO_set_accept_port(3), BIO_get_accept_name(3), BIO_get_accept_port(3), BIO_new_accept(3), BIO_set_nbio_accept(3), BIO_set_accept_bios(3), BIO_get_peer_name(3), BIO_get_peer_port(3), BIO_get_accept_ip_family(3), BIO_set_accept_ip_family(3), BIO_set_bind_mode(3), BIO_get_bind_mode(3), BIO_do_accept(3)
accept BIO
BIO_socket(3), BIO_bind(3), BIO_connect(3), BIO_listen(3), BIO_accept_ex(3), BIO_closesocket(3)
BIO socket communication setup routines
SSL_CTX_sess_number(3), SSL_CTX_sess_connect(3), SSL_CTX_sess_connect_good(3), SSL_CTX_sess_connect_renegotiate(3), SSL_CTX_sess_accept(3), SSL_CTX_sess_accept_good(3), SSL_CTX_sess_accept_renegotiate(3), SSL_CTX_sess_hits(3), SSL_CTX_sess_cb_hits(3), SSL_CTX_sess_misses(3), SSL_CTX_sess_timeouts(3), SSL_CTX_sess_cache_full(3)
obtain session cache statistics
SSL_accept(3)
wait for a TLS/SSL client to initiate a TLS/SSL handshake
SSL_in_before(3), SSL_in_init(3), SSL_is_init_finished(3), SSL_in_connect_init(3), SSL_in_accept_init(3), SSL_get_state(3)
retrieve information about the handshake state machine
SSL_set_connect_state(3), SSL_get_accept_state(3)
prepare SSL object to work in client or server mode
SSL_set_connect_state(3), SSL_set_accept_state(3), SSL_is_server(3)
functions for manipulating and examining the client or server mode of an SSL object
BIO_s_accept(3), BIO_set_accept_name(3), BIO_set_accept_port(3), BIO_get_accept_name(3), BIO_get_accept_port(3), BIO_new_accept(3), BIO_set_nbio_accept(3), BIO_set_accept_bios(3), BIO_get_peer_name(3), BIO_get_peer_port(3), BIO_get_accept_ip_family(3), BIO_set_accept_ip_family(3), BIO_set_bind_mode(3), BIO_get_bind_mode(3), BIO_do_accept(3)
accept BIO
BIO_socket(3), BIO_bind(3), BIO_connect(3), BIO_listen(3), BIO_accept_ex(3), BIO_closesocket(3)
BIO socket communication setup routines
CURLOPT_ACCEPTTIMEOUT_MS(3)
timeout waiting for FTP server to connect back
CURLOPT_ACCEPT_ENCODING(3)
enables automatic decompression of HTTP downloads
MPI_Comm_accept(3)
Accept a request to form a new intercommunicator
OSSL_CMP_SRV_process_request(3), OSSL_CMP_CTX_server_perform(3), OSSL_CMP_SRV_CTX_new(3), OSSL_CMP_SRV_CTX_free(3), OSSL_CMP_SRV_cert_request_cb_t(3), OSSL_CMP_SRV_rr_cb_t(3), OSSL_CMP_SRV_certConf_cb_t(3), OSSL_CMP_SRV_genm_cb_t(3), OSSL_CMP_SRV_error_cb_t(3), OSSL_CMP_SRV_pollReq_cb_t(3), OSSL_CMP_SRV_CTX_init(3), OSSL_CMP_SRV_CTX_get0_cmp_ctx(3), OSSL_CMP_SRV_CTX_get0_custom_ctx(3), OSSL_CMP_SRV_CTX_set_send_unprotected_errors(3), OSSL_CMP_SRV_CTX_set_accept_unprotected(3), OSSL_CMP_SRV_CTX_set_accept_raverified(3), OSSL_CMP_SRV_CTX_set_grant_implicit_confirm(3)
generic functions to set up and control a CMP server
SSL_CTX_sess_number(3), SSL_CTX_sess_connect(3), SSL_CTX_sess_connect_good(3), SSL_CTX_sess_connect_renegotiate(3), SSL_CTX_sess_accept(3), SSL_CTX_sess_accept_good(3), SSL_CTX_sess_accept_renegotiate(3), SSL_CTX_sess_hits(3), SSL_CTX_sess_cb_hits(3), SSL_CTX_sess_misses(3), SSL_CTX_sess_timeouts(3), SSL_CTX_sess_cache_full(3)
obtain session cache statistics
SSL_accept(3)
wait for a TLS/SSL client to initiate a TLS/SSL handshake
SSL_in_before(3), SSL_in_init(3), SSL_is_init_finished(3), SSL_in_connect_init(3), SSL_in_accept_init(3), SSL_get_state(3)
retrieve information about the handshake state machine
SSL_set_connect_state(3), SSL_set_accept_state(3), SSL_is_server(3)
functions for manipulating and examining the client or server mode of an SSL object
XkbGetSlowKeysDelay(3)
Gets the SlowKeys acceptance delay for a keyboard device
XtCallAcceptFocus(3)
calla widget's accept_focus procedure
accept_check(1)
Check whether a grammar accept / reject given word sequences
cupsaccept(8), cupsaccept/cupsreject(8)
accept/reject jobs sent to a destination
ezmlm-accept(1)
accept messages in moderation queue
ezmlm-moderate(1)
process moderator actions for message acceptance and rejection
fi_cm(3)
Connection management operations fi_connect / fi_listen / fi_accept / fi_reject / fi_shutdown Manage endpoint connection state. fi_setname / fi_getname / fi_getpeer Set local, or return local or peer endpoint address. fi_join / fi_close / fi_mc_addr Join, leave, or retrieve a multicast address
fsaparse(3gv)
parse a word-acceptor automaton file
getstr(3x), getnstr(3x), wgetstr(3x), wgetnstr(3x), mvgetstr(3x), mvgetnstr(3x), mvwgetstr(3x), mvwgetnstr(3x)
accept character strings from curses terminal keyboard
gmx-bar(1)
Calculate free energy difference estimates through Bennett's acceptance ratio rst2man-indent-level 0 1 rstReportMargin \$1
gss_accept_sec_context(3), gss_acquire_cred(3), gss_add_cred(3), gss_add_oid_set_member(3), gss_canonicalize_name(3), gss_compare_name(3), gss_context_time(3), gss_create_empty_oid_set(3), gss_delete_sec_context(3), gss_display_name(3), gss_display_status(3), gss_duplicate_name(3), gss_export_name(3), gss_export_sec_context(3), gss_get_mic(3), gss_import_name(3), gss_import_sec_context(3), gss_indicate_mechs(3), gss_init_sec_context(3), gss_inquire_context(3), gss_inquire_cred(3), gss_inquire_cred_by_mech(3), gss_inquire_mechs_for_name(3), gss_inquire_names_for_mech(3), gss_krb5_ccache_name(3), gss_krb5_compat_des3_mic(3), gss_krb5_copy_ccache(3), gss_krb5_import_cred gsskrb5_extract_authz_data_from_sec_context(3), gsskrb5_register_acceptor_identity(3), gss_krb5_import_ccache(3), gss_krb5_get_tkt_flags(3), gss_process_context_token(3), gss_release_buffer(3), gss_release_cred(3), gss_release_name(3), gss_release_oid_set(3), gss_seal(3), gss_sign(3), gss_test_oid_set_member(3), gss_unseal(3), gss_unwrap(3), gss_verify(3), gss_verify_mic(3), gss_wrap(3), gss_wrap_size_limit(3)
Generic Security Service Application Program Interface library
gup(1)
A G roup U pdate P rogram that accepts commands by mail to edit a newsgroup subscription file for subsequent use by news systems such as INN and C-News
ipc_accept(3)
accepts an incoming IPC connection
ipc_accept_mem(3)
accepts an incoming IPC connection
irs(1)
Accept incoming OBEX and COMM connections on IrDA
libowfat_socket_accept4(3), socket_accept4(3)
accept an IPv4 TCP connection on a socket
libowfat_socket_accept6(3), socket_accept6(3)
accept an IPv6 TCP connection on a socket
libssh2_channel_forward_accept(3)
accept a queued connection
lightning-invoice(7)
Command for accepting payments
mini_sendmail(8)
accept email on behalf of real sendmail
modbus_tcp_accept(3)
accept a new connection on a TCP Modbus socket (IPv4)
modbus_tcp_pi_accept(3)
accept a new connection on a TCP PI Modbus socket (IPv6)
nsca-ng(8)
monitoring command acceptor
ofmipd(8)
accept outgoing mail through OFMIP
pvm_recvf(3)
Redefines the comparison function used to accept messages
qconfirm-accept(1)
confirms delivery of pending messages held by qconfirm-check
rnews(8cn), cunbatch(8cn)
accept and spool news input newsspool, newsrun - news input spooler and processing newsrunning - control news-processing daemon
rwreceiver(8)
Accepts files transferred from rwsender(s)
tcp_accept(3)
accepts an incoming TCP connection
tcp_accept_mem(3)
accepts an incoming TCP connection
tcpserver(1)
accepts incoming TCP connections
tls_accept_socket(3), tls_accept_fds(3), tls_accept_cbs(3)
accept an incoming client connection in a TLS server
xs_bind(3)
accept connections on a socket
zfs-jail(8)
Attaches and detaches ZFS filesystems from FreeBSD jails. A Tn ZFS dataset can be attached to a jail by using the Cm jail subcommand. You cannot attach a dataset to one jail and the children of the same dataset to another jail. You can also not attach the root file system of the jail or any dataset which needs to be mounted before the zfs rc script is run inside the jail, as it would be attached unmounted until it is mounted from the rc script inside the jail. To allow management of the dataset from within a jail, the jailed property has to be set and the jail needs access to the /dev/zfs device. The quota property cannot be changed from within a jail. See jail(8) for information on how to allow mounting ZFS datasets from within a jail. A Tn ZFS dataset can be detached from a jail using the Cm unjail subcommand. After a dataset is attached to a jail and the jailed property is set, a jailed file system cannot be mounted outside the jail, since the jail administrator might have set the mount point to an unacceptable value
zmq_bind(3)
accept incoming connections on a socket
zmq_unbind(3)
Stop accepting connections on a socket
Authen::Passphrase::AcceptAll(3)
accept any passphrase
Bio::DB::Taxonomy::list(3)
An implementation of Bio::DB::Taxonomy that accepts lists of words to build a database
Catalyst::Component::ACCEPT_CONTEXT(3)
Make the current Catalyst request context available in Models and Views
Class::Workflow::State::AcceptHooks(3)
Add hooks that are fired when the state accepts an instance
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
Glib::OptionContext(3)
defines options accepted by the commandline option parser
HTML::FormHandler::Field::Hour(3)
accept integer from 0 to 23
HTTP::Headers::ActionPack::AcceptCharset(3)
A Priority List customized for Media Types
HTTP::Headers::ActionPack::AcceptLanguage(3)
A Priority List customized for Media Types
HTTP::Throwable::Role::Status::NotAcceptable(3)
406 Not Acceptable
I18N::AcceptLanguage(3)
Matches language preference to available languages
IO::Async::LoopTests(3), "IO::Async::LoopTests"(3)
acceptance testing for IO::Async::Loop subclasses
IOC::Service::Parameterized(3)
An IOC Service object which accepts a set of parameters for the instance
Jifty::Plugin::Deflater(3)
Handles Accept-Encoding and compression
Log::Dispatch::Null(3)
Object that accepts messages and does nothing
MPI_Comm_accept(3), MPI_Comm_accept (3)
Establishes communication with a client
MPI_Open_port(3)
Establishes a network address for a server to accept connections from clients
MooseX::OneArgNew(3)
teach ->new to accept single, non-hashref arguments
Net::DBus::Binding::Server(3)
A server to accept incoming connections
POE::Wheel::ListenAccept(3)
accept connections from regular listening sockets
Paws::EC2::AcceptVpcPeeringConnection(3)
Arguments for method AcceptVpcPeeringConnection on Paws::EC2
Reflex::Acceptor(3)
a non-blocking server (client socket acceptor)
Reflex::Role::Accepting(3)
add connection accepting to a class
Rose::HTML::Form::Field::Email(3)
Text field that only accepts valid email addresses
Rose::HTML::Form::Field::Integer(3)
Text field that only accepts integer values
Rose::HTML::Form::Field::Numeric(3)
Text field that only accepts numeric values
Rose::HTML::Form::Field::PhoneNumber::US(3)
Text field that accepts only input that contains exactly 10 digits, and coerces valid input into US phone numbers in the form: 123-456-7890
Rose::HTML::Form::Field::Set(3)
Text area that accepts whitespace- or comma-separated strings
Rose::HTML::Form::Field::Time(3)
Text field that accepts only valid times and coerces valid input into HH:MM:SS AM/PM format
Rose::HTML::Form::Field::Time::Hours(3)
Text field that only accepts valid hours
Rose::HTML::Form::Field::Time::Minutes(3)
Text field that only accepts valid minutes
Rose::HTML::Form::Field::Time::Seconds(3)
Text field that only accepts valid seconds
Sisimai::Reason::NotAccept(3)
Bounce reason is "notaccept" or not
XML::Compile::SOAP::Daemon(3)
SOAP accepting server (base class)
dial(3), announce(3), listen(3), accept(3), reject(3), netmkaddr(3), getnetconninfo(3), freenetconninfo(3), dialparse(3)
make and break network connections
disputes(7)
Handling Module Name Disputes This document describes the steps that you should take to resolve module name disputes with other npm publishers. It also describes special steps you should take about names you think infringe your trademarks. This document is a clarification of the acceptable behavior outlined in the npm Code of Conduct https://www.npmjs.com/policies/conduct, and nothing in this document should be interpreted to contradict any aspect of the npm Code of Conduct
getstr(3x), getnstr(3x), wgetstr(3x), wgetnstr(3x), mvgetstr(3x), mvgetnstr(3x), mvwgetstr(3x), mvwgetnstr(3x)
accept character strings from curses terminal keyboard
home | help