| /freebsd/share/examples/etc/ |
| H A D | README.examples | 10 apmd.conf - configuration file for apmd(8)
17 devd.conf - configuration file for devd(8)
18 devfs.conf - configuration file for devfs(8)
21 fbtab - configuration file for login(1)
29 inetd.conf - configuration file for inetd(8)
30 locate.rc - configuration file for locate(1)
37 netconfig - network configuration data base
42 nsmb.conf - smbfs lookups configuration file
43 pf.conf - pf(4) example configuration file
46 printcap - configuration file for lpr(1)
[all …]
|
| /freebsd/usr.sbin/nscd/ |
| H A D | config.h | 95 struct configuration { struct
118 struct configuration *init_configuration(void); argument
119 void destroy_configuration(struct configuration *);
120 void fill_configuration_defaults(struct configuration *);
122 int add_configuration_entry(struct configuration *,
126 size_t configuration_get_entries_size(struct configuration *);
127 struct configuration_entry *configuration_get_entry(struct configuration *,
129 struct configuration_entry *configuration_find_entry(struct configuration *,
139 void configuration_lock_rdlock(struct configuration *config);
140 void configuration_lock_wrlock(struct configuration *config);
[all …]
|
| H A D | parser.c | 62 static void set_threads_num(struct configuration *, int);
91 find_create_entry(struct configuration *config, in find_create_entry()
126 set_positive_time_to_live(struct configuration *config, in set_positive_time_to_live()
148 set_negative_time_to_live(struct configuration *config, in set_negative_time_to_live()
204 set_keep_hot_count(struct configuration *config, in set_keep_hot_count()
225 set_positive_policy(struct configuration *config, in set_positive_policy()
241 set_negative_policy(struct configuration *config, in set_negative_policy()
257 set_perform_actual_lookups(struct configuration *config, in set_perform_actual_lookups()
273 set_suggested_size(struct configuration *config, in set_suggested_size()
356 set_threads_num(struct configuration *config, int value) in set_threads_num()
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | CONF_modules_load_file.pod | 7 - OpenSSL configuration functions
24 configuration file pathname as follows.
43 reads configuration information from B<cnf>.
68 ignore missing configuration files. Normally a missing configuration file
82 consider a configuration file error as fatal and exit immediately.
100 fprintf(stderr, "FATAL: error loading configuration file\n");
116 missing configuration file ignored:
132 fprintf(stderr, "Error opening configuration file\n");
133 /* Other missing configuration file behaviour */
139 /* Other malformed configuration file behaviour */
[all …]
|
| H A D | OPENSSL_load_builtin_modules.pod | 5 …d_builtin_modules, ASN1_add_oid_module, ENGINE_add_conf_module - add standard configuration modules
18 configuration modules to the internal list. They can then be used by the
19 OpenSSL configuration code.
23 ENGINE_add_conf_module() adds just the ENGINE configuration module.
27 If the simple configuration function OPENSSL_config() is called then
30 Applications which use the configuration functions directly will need to
32 configuration code.
35 configuration modules instead of adding modules selectively: otherwise
|
| H A D | SSL_CTX_config.pod | 17 B<SSL> structure using the configuration B<name>.
20 complex tasks based on the contents of the configuration file: greatly
21 simplifying application configuration code. A degree of future proofing
22 can also be achieved: an application can support configuration features
25 A configuration file must have been previously loaded, for example using
26 CONF_modules_load_file(). See L<config(5)> for details of the configuration
41 # list of configuration modules
|
| H A D | CONF_modules_free.pod | 6 OpenSSL configuration cleanup functions
24 configuration modules. Normally, in versions of OpenSSL prior to 1.1.0,
26 CONF_modules_free() at exit to tidy up any configuration performed.
28 CONF_modules_finish() calls each configuration modules B<finish> handler
29 to free up any configuration that module may have performed.
31 CONF_modules_unload() finishes and unloads configuration modules. If
|
| H A D | OPENSSL_config.pod | 5 OPENSSL_config, OPENSSL_no_config - simple OpenSSL configuration functions
26 OPENSSL_no_config() disables configuration. If called before OPENSSL_config()
27 no configuration takes place.
38 control over their configuration functionality should use the configuration
44 There are several reasons why calling the OpenSSL configuration routines is
51 configuration file.
|
| /freebsd/tools/kerneldoc/ |
| H A D | Doxyfile | 4 # Project related configuration options
30 # Build related configuration options
65 # configuration options related to the input files
81 # configuration options related to source browsing
96 # configuration options related to the HTML output
116 # configuration options related to the LaTeX output
131 # configuration options related to the RTF output
140 # configuration options related to the man page output
147 # configuration options related to the XML output
155 # configuration options for the AutoGen Definitions output
[all …]
|
| /freebsd/crypto/heimdal/doc/ |
| H A D | doxytmpl.dxy | 2 # Project related configuration options
41 # Build related configuration options
80 # configuration options related to the input files
122 # configuration options related to source browsing
139 # configuration options related to the HTML output
158 # configuration options related to the LaTeX output
173 # configuration options related to the RTF output
182 # configuration options related to the man page output
189 # configuration options related to the XML output
197 # configuration options for the AutoGen Definitions output
[all …]
|
| /freebsd/tools/kerneldoc/subsys/ |
| H A D | common-Doxyfile | 4 # Project related configuration options
42 # Build related configuration options
80 # configuration options related to the input files
134 # configuration options related to source browsing
151 # configuration options related to the HTML output
170 # configuration options related to the LaTeX output
185 # configuration options related to the RTF output
194 # configuration options related to the man page output
201 # configuration options related to the XML output
207 # configuration options for the AutoGen Definitions output
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 3 Hardware modules that control pin multiplexing or configuration parameters
8 Hardware modules whose signals are affected by pin configuration are
22 configuration used by those states.
47 pinctrl-0: List of phandles, each pointing at a pin configuration
48 node. These referenced pin configuration nodes must be child
53 contributing part of the overall configuration. See the next
55 pin configuration nodes.
65 pinctrl-1: List of phandles, each pointing at a pin configuration
68 pinctrl-n: List of phandles, each pointing at a pin configuration
90 * For an IP block whose binding supports pin configuration,
[all …]
|
| H A D | sprd,pinctrl.txt | 7 to configure for some global common configuration, such as domain
15 There are too much various configuration that we can not list all
16 of them, so we can not make every Spreadtrum-special configuration
17 as one generic configuration, and maybe it will add more strange
18 global configuration in future. Then we add one "sprd,control" to
19 set these various global control configuration, and we need use
30 configuration.
34 related configuration are:
43 configuration, to set the pin sleep related configuration automatically
46 and set the pin sleep related configuration as "input-enable", which
|
| H A D | qcom,apq8064-pinctrl.txt | 24 phrase "pin configuration node".
26 Qualcomm's pin configuration nodes act as a container for an arbitrary number of
27 subnodes. Each of these subnodes represents some desired configuration for a
28 pin, a group, or a list of pins or groups. This configuration can include the
29 mux function to select on those pin(s)/group(s), and various pin configuration
36 other words, a subnode that lists a mux function but no pin configuration
37 parameters implies no information about any pin configuration parameters.
43 to specify in a pin configuration subnode:
|
| H A D | ste,nomadik.txt | 12 phrase "pin configuration node".
14 ST Ericsson's pin configuration nodes act as a container for an arbitrary number of
15 subnodes. Each of these subnodes represents some desired configuration for a
16 pin, a group, or a list of pins or groups. This configuration can include the
17 mux function to select on those pin(s)/group(s), and various pin configuration
32 Required pin configuration subnode properties:
33 - pins: A string array describing the pins affected by the configuration
35 - ste,config: Handle of pin configuration node
56 3: sleep input and keep last input configuration (no pull, pull up or pull down).
|
| H A D | oxnas,pinctrl.txt | 7 OXNAS 'pin configuration node' is a node of a group of pins which can be
9 pins, optional function, and optional mux related configuration.
15 Required properties for pin configuration sub-nodes:
16 - pins: List of pins to which the configuration applies.
18 Optional properties for pin configuration sub-nodes:
|
| H A D | qcom,ipq4019-pinctrl.txt | 27 phrase "pin configuration node".
29 The pin configuration nodes act as a container for an arbitrary number of
30 subnodes. Each of these subnodes represents some desired configuration for a
31 pin, a group, or a list of pins or groups. This configuration can include the
32 mux function to select on those pin(s)/group(s), and various pin configuration
39 other words, a subnode that lists a mux function but no pin configuration
40 parameters implies no information about any pin configuration parameters.
46 to specify in a pin configuration subnode:
|
| H A D | xlnx,zynq-pinctrl.txt | 10 phrase "pin configuration node".
12 Zynq's pin configuration nodes act as a container for an arbitrary number of
13 subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those pin(s)/group(s), and various pin configuration
18 Each configuration node can consist of multiple nodes describing the pinmux and
29 Required properties for configuration nodes:
69 a pin configuration subnode:
|
| /freebsd/crypto/openssl/demos/bio/ |
| H A D | cmod.cnf | 1 # Example config module configuration
4 # and section containing configuration
7 # Comment out the next line to ignore configuration errors
11 # list of configuration modules
13 # SSL configuration module
|
| /freebsd/crypto/openssh/ |
| H A D | README.tun | 9 a network configuration specific to the OpenBSD operating system.
14 have to add the following option to the ssh server configuration file
20 reread it's configuration.
26 automatically start the related interface configuration command. These
33 Use the hostname.if(5) interface-specific configuration file to set up
34 the network tunnel configuration with OpenBSD. For example, use the
35 following configuration in /etc/hostname.tun0 to set up the layer 3
64 A more complicated configuration is possible to establish a tunnel to
66 The following example describes a client configuration to connect to
83 The following network plan illustrates the previous configuration in
[all …]
|
| /freebsd/crypto/openssl/doc/man1/ |
| H A D | openssl-fipsinstall.pod.in | 6 openssl-fipsinstall - perform FIPS configuration installation
31 This command is used to generate a FIPS module configuration file.
32 This configuration file can be used each time a FIPS module is loaded
37 The generated configuration file consists of:
92 Input filename to load configuration data from.
101 Name of the provider inside the configuration file.
106 Name of the section inside the configuration file.
194 data that is included by the base C<parent_config> configuration file.
210 when generating the fips configuration file.
215 for the module, and save the F<fips.cnf> configuration file:
[all …]
|
| /freebsd/contrib/file/magic/Magdir/ |
| H A D | sendmail | 10 # READ.ME.FIRST.AWP Sendmail frozen configuration
12 # Email_23_f217153422.ts Sendmail frozen configuration
16 # freezed configuration file (dbm format?) created from sendmail.cf with -bz
17 # by older sendmail. til version 8.6 support for frozen configuration files is removed
20 >16 regex/s =^[0-78][0-9.]{4} Sendmail frozen configuration
26 >16 regex/s =^[0-78][0-9.]{4} Sendmail frozen configuration
|
| /freebsd/sys/contrib/libsodium/ |
| H A D | appveyor.yml | 8 configuration: Debug
10 configuration: Release
12 configuration: Debug
14 configuration: Release
|
| /freebsd/contrib/wpa/wpa_supplicant/ |
| H A D | README-WPS | 15 passphrase/PSK) and configuration of an access point and client
17 with PIN method and push-button configuration (PBC) being the most
53 wpa_supplicant configuration
82 The network configuration blocks needed for WPS are added
84 to be added explicitly in the configuration file.
89 to allow configuration file updates:
159 current AP configuration and optionally, to configure an AP,
171 In order to change the AP configuration, the new configuration
213 its configuration internally. However, it is possible to
219 configuration based on them.
[all …]
|
| /freebsd/contrib/llvm-project/lldb/source/API/ |
| H A D | SBTrace.cpp | 93 SBError SBTrace::Start(const SBStructuredData &configuration) { in Start() argument
94 LLDB_INSTRUMENT_VA(this, configuration); in Start()
99 m_opaque_sp->Start(configuration.m_impl_up->GetObjectSP())) in Start()
105 const SBStructuredData &configuration) { in Start() argument
106 LLDB_INSTRUMENT_VA(this, thread, configuration); in Start()
114 configuration.m_impl_up->GetObjectSP())) in Start()
|