| /freebsd/share/examples/etc/ |
| H A D | README.examples | 10 apmd.conf - configuration file for apmd(8)
16 defaults/ - directory containing default configuration file
17 devd.conf - configuration file for devd(8)
18 devfs.conf - configuration file for devfs(8)
19 dhclient.conf - configuration file for dhclient(8)
21 fbtab - configuration file for login(1)
23 gettytab - defines port configuration for getty(8)
29 inetd.conf - configuration file for inetd(8)
30 locate.rc - configuration file for locate(1)
31 login.access - configuration file for login(8) (see login.access(5))
[all …]
|
| /freebsd/usr.sbin/nscd/ |
| H A D | config.h | 93 * Contains global configuration options and array of all configuration entries
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 *,
99 entriesconfiguration global() argument
[all...] |
| H A D | parser.c | 41 static void enable_cache(struct configuration *,const char *, int);
42 static struct configuration_entry *find_create_entry(struct configuration *,
48 static void check_files(struct configuration *, const char *, int);
49 static void set_keep_hot_count(struct configuration *, const char *, int);
50 static void set_negative_policy(struct configuration *, const char *,
52 static void set_negative_time_to_live(struct configuration *,
54 static void set_positive_policy(struct configuration *, const char *,
56 static void set_perform_actual_lookups(struct configuration *, const char *,
58 static void set_positive_time_to_live(struct configuration *,
60 static void set_suggested_size(struct configuration *, cons
[all...] |
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | CONF_modules_load_file.pod | 7 - OpenSSL configuration functions
24 configuration file pathname as follows.
32 If B<filename> is NULL the standard OpenSSL configuration file is used
43 reads configuration information from B<cnf>.
50 configuration modules are ignored. If not set the first module error is
59 the default system-wide configuration file, as having all OpenSSL applications
64 If B<CONF_MFLAGS_NO_DSO> is set configuration module loading from DSOs is
68 ignore missing configuration files. Normally a missing configuration file
75 application can customise application configuration to best suit its needs.
76 In some cases the use of a configuration file is optional and its absence is not
[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
56 # configuration options related to warning and progress messages
65 # configuration options related to the input files
81 # configuration options related to source browsing
90 # configuration options related to the alphabetical class index
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
[all …]
|
| /freebsd/crypto/heimdal/doc/ |
| H A D | doxytmpl.dxy | 2 # Project related configuration options
41 # Build related configuration options
71 # configuration options related to warning and progress messages
80 # configuration options related to the input files
122 # configuration options related to source browsing
133 # configuration options related to the alphabetical class index
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
[all …]
|
| /freebsd/tools/kerneldoc/subsys/ |
| H A D | common-Doxyfile | 4 # Project related configuration options
42 # Build related configuration options
69 # configuration options related to warning and progress messages
80 # configuration options related to the input files
134 # configuration options related to source browsing
145 # configuration options related to the alphabetical class index
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
[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
14 single static pin configuration, e.g. set up during initialization. Others
22 configuration used by those states.
26 driver loads. This would allow representing a board's static pin configuration
31 they require certain specific named states for dynamic pin configuration.
37 property exists to define the pin configuration. Each state may also be
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
[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 automaticall
[all...] |
| 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 | 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 | qcom,ipq8064-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 | qcom,msm8660-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 | 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
55 remote host by default, use the following ssh client configuration for
64 A more complicated configuration is possible to establish a tunnel to
66 The following example describes a client configuration to connect to
[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/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:
88 Filename to output the configuration data to; the default is standard output.
92 Input filename to load configuration data from.
97 Verify that the input configuration file contains the correct information.
101 Name of the provider inside the configuration file.
106 Name of the section inside the configuration file.
170 "MAC status indicator" to the output configuration file. Without these fields
[all …]
|
| /freebsd/contrib/wpa/wpa_supplicant/ |
| H A D | README-WPS | 13 Wi-Fi Protected Setup (WPS) is a mechanism for easy configuration of a
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
57 wpa_supplicant build configuration (.config). Here is an example
58 configuration that includes WPS support and Linux nl80211-based
75 the device. This is configured in the runtime configuration for
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:
[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()
|