Searched refs:sufficient (Results 1 – 25 of 123) sorted by relevance
12345
7 #auth sufficient pam_krb5.so no_warn try_first_pass8 #auth sufficient pam_ssh.so no_warn try_first_pass22 #password sufficient pam_krb5.so no_warn try_first_pass
7 #auth sufficient pam_krb5.so no_warn try_first_pass8 #auth sufficient pam_ssh.so no_warn try_first_pass
7 auth sufficient pam_rootok.so no_warn8 auth sufficient pam_self.so no_warn
7 #auth sufficient pam_krb5.so no_warn8 #auth sufficient pam_ssh.so no_warn try_first_pass
37 sufficient: success is sufficient, and if no previous required39 binding: success is sufficient; on failure all remaining57 Note that having a "sufficient" module as the last entry for a
7 auth sufficient pam_self.so no_warn
16 It's observed that 5ms is sufficient.
25 for the I/V sense data is not sufficient, the device can also be configured
23 // used, which should be sufficient.
40 responsibility to ensure sufficient memory is allocated at I<*fds> so typically49 sufficient memory allocated, although they may be NULL. The number of added fds
40 as well, so it is sufficient to check the return value of the last
68 sufficient memory has been allocated in I<*fd> to receive all the file72 the number of fds, and then again when sufficient memory has been allocated. If84 NULL then the caller is responsible for ensuring sufficient memory is allocated.
42 on the 16-bit DOS platform). This should be sufficient for usual certificate
24 to the build system, so it should be documented in sufficient detail and
41 "interrupt-parent" and "interrupts" are usually sufficient):
37 sufficient to restart the entire system