| /freebsd-14.2/sys/contrib/openzfs/tests/zfs-tests/tests/functional/rsend/ |
| H A D | rsend_012_pos.ksh | 47 typeset behaviour=$1 52 case $behaviour in 67 log_fail "Unrecognized behaviour: $behaviour"
|
| /freebsd-14.2/tests/sys/cddl/zfs/tests/rsend/ |
| H A D | rsend_012_pos.ksh | 71 typeset behaviour=$1 75 case $behaviour in 103 log_fail "Unrecognized behaviour: $behaviour"
|
| /freebsd-14.2/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_set_quiet_shutdown.pod | 5 …_get_quiet_shutdown, SSL_set_quiet_shutdown, SSL_get_quiet_shutdown - manipulate shutdown behaviour 45 is sent to the peer. This behaviour violates the TLS standard. 47 The default is normal shutdown behaviour as described by the TLS standard.
|
| H A D | CONF_modules_load_file.pod | 36 The behaviour can be customized using B<flags>. Note that, the error suppressing 133 /* Other missing configuration file behaviour */ 139 /* Other malformed configuration file behaviour */ 143 /* Other configuration error behaviour */
|
| H A D | SSL_CTX_set_session_ticket_cb.pod | 122 If the callback does not wish to change the default ticket behaviour then it 132 If the callback does not wish to change the default ticket behaviour then it 141 If the callback does not wish to change the default ticket behaviour then it 158 default behaviour is to always issue a new ticket on resumption. In both cases 159 this behaviour can be changed if a ticket key callback is in use (see
|
| H A D | SSL_CTX_set_cert_verify_callback.pod | 31 By setting I<callback> to NULL, the default behaviour is restored. 36 In client mode, the behaviour is as follows. 82 and in most cases it should be sufficient to modify its behaviour using
|
| H A D | SSL_set_fd.pod | 23 inherit the behaviour of B<fd>. If B<fd> is nonblocking, the B<ssl> will 24 also have nonblocking behaviour.
|
| H A D | d2i_X509.pod | 449 The reason for this-auto increment behaviour is to reflect a typical 596 In some versions of OpenSSL the "reuse" behaviour of B<d2i_I<TYPE>>() when 599 OpenSSL prior to 1.1.0, when the "reuse" behaviour is used and an error occurs 600 the behaviour is inconsistent. Some functions behaved as described here, while 603 As a result of the above issues the "reuse" behaviour is strongly discouraged.
|
| H A D | SSL_set_bio.pod | 18 object. The SSL engine inherits the behaviour of B<rbio>. If the BIO is 19 nonblocking then the B<ssl> object will also have nonblocking behaviour. This
|
| H A D | SSL_get_peer_tmp_key.pod | 27 behaviour on the server end is release-dependent.
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/ |
| H A D | ABI.rst | 15 then default to the previous behaviour if it is missing. If a binding 32 behaviour when a newly added property is missing.
|
| /freebsd-14.2/contrib/sendmail/cf/feature/ |
| H A D | notsticky.m4 | 19 # the old default behaviour.
|
| /freebsd-14.2/contrib/llvm-project/lld/docs/ |
| H A D | WebAssembly.rst | 6 behaviour of traditional ELF linkers and specifically the ELF lld port. Where 145 behaviour of a traditional ELF linker, and in particular the ELF port of lld. 155 the target signature. Even though this is undefined behaviour in C/C++, it is not 165 The default behaviour is to generate these stub function and to produce 166 a warning. The ``--fatal-warnings`` flag can be used to disable this behaviour
|
| /freebsd-14.2/crypto/openssl/test/ssl-tests/ |
| H A D | 18-dtls-renegotiate.cnf.in | 68 # handshake support was first added. Neither behaviour is wrong, but the 69 # discrepancy is strange. TODO: Should we harmonise the TLS and DTLS behaviour,
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/power/supply/ |
| H A D | axp20x_usb_power.txt | 9 The AXP223 PMIC shares most of its behaviour with the AXP221 but has slight
|
| H A D | x-powers,axp20x-usb-power-supply.yaml | 10 The AXP223 PMIC shares most of its behaviour with the AXP221 but has slight
|
| H A D | sbs,sbs-manager.txt | 17 behaviour. So standard i2c-mux nodes can be used to register up to four slave
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/media/ |
| H A D | renesas,fcp.txt | 10 for FDP (FCPF). Their configuration and behaviour depend on the module they
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | aspeed-scu.txt | 1 The Aspeed System Control Unit manages the global behaviour of the SoC,
|
| /freebsd-14.2/bin/sh/tests/expansion/ |
| H A D | assign1.0 | 27 # expect sensible behaviour, although it disagrees with POSIX
|
| H A D | plus-minus3.0 | 23 # We follow original ash behaviour for quoted ${var+-=?} expansions:
|
| /freebsd-14.2/crypto/openssh/ |
| H A D | README.platform | 21 to force the previous IPv4-only behaviour. 93 PAM is enabled. To maintain existing behaviour, pam_nologin should be
|
| /freebsd-14.2/crypto/openssl/doc/man1/ |
| H A D | CA.pl.pod | 40 use by a beginner. Its behaviour isn't always what is wanted. For more control 41 over the behaviour of the certificate commands call the L<openssl(1)> command 92 the B<-newca> option terminated abnormally. To get the correct behaviour
|
| /freebsd-14.2/crypto/openssl/doc/man7/ |
| H A D | EVP_MD-common.pod | 32 Diverse flags that describe exceptional behaviour for the digest.
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/arm/tegra/ |
| H A D | nvidia,tegra30-actmon.txt | 3 The activity monitor block collects statistics about the behaviour of other
|