Searched refs:contacted (Results 1 – 25 of 26) sorted by relevance
12
| /netbsd/src/crypto/dist/ipsec-tools/src/racoon/ |
| D | handler.h | 369 struct contacted { struct
371 LIST_ENTRY(contacted) chain; argument
517 extern struct contacted *getcontacted(struct sockaddr *);
|
| D | handler.c | 87 static LIST_HEAD(_ctdtree_, contacted) ctdtree;
915 struct contacted *
918 struct contacted *p; in getcontacted()
934 struct contacted *new; in inscontacted()
957 struct contacted *p, *next; in remcontacted()
|
| /netbsd/src/external/gpl3/binutils/dist/binutils/ |
| D | SECURITY.txt | 54 The team contacted will take care of details such as vulnerability
|
| /netbsd/src/crypto/dist/ipsec-tools/src/racoon/doc/ |
| D | FAQ | 34 be contacted by racoonctl(8).
|
| /netbsd/src/external/bsd/libbind/dist/doc/ |
| D | hesiod.cat3 | 65 … _h_e_s_i_o_d___r_e_s_o_l_v_e failed because no name server could be contacted
|
| D | resolver.cat3 | 285 the response. In this case, only one nameserver will be contacted. The
|
| /netbsd/src/external/gpl3/gdb/dist/gdb/ |
| D | SECURITY.txt | 214 The team contacted will take care of details such as vulnerability
|
| /netbsd/src/external/bsd/openldap/dist/doc/guide/admin/ |
| D | appendix-common-errors.sdf | 15 server cannot be contacted. This may occur for many reasons:
133 itself back to a server it already contacted. The server responds as it did
|
| D | backends.sdf | 85 server is moved to the head, so that it will be first contacted the next time
|
| /netbsd/src/external/bsd/openldap/dist/doc/rfc/ |
| D | rfc4511.txt | 634 The referral result code indicates that the contacted server cannot
655 when other servers would need to be contacted to complete the
1638 For example, suppose the contacted server (hosta) holds the entry
1644 <DC=Example,DC=NET> is requested to the contacted server, it may
1658 generated. Continuing the example, if the client contacted the
1670 requested to the contacted server, it may return the following:
1687 If the contacted server does not hold the base object for the Search,
|
| D | rfc3296.txt | 289 For example, suppose the contacted server (hosta) holds the entry
|
| D | rfc4512.txt | 2082 that may be contacted when this server becomes unavailable. URIs for
|
| /netbsd/src/external/bsd/openldap/dist/doc/drafts/ |
| D | draft-joslin-config-schema-xx.txt | 491 the preferredServerList MUST be contacted before attempting to
571 contacted only if the preferredServerList attribute is also
|
| D | draft-ietf-ldapext-ldap-c-api-xx.txt | 855 actually contacted until an operation is performed that requires it,
1491 Note that if an LDAPv2 server is contacted, no other operations over the
|
| D | draft-sermersheim-ldap-distproc-xx.txt | 620 DSA and DN that has already been contacted while attempting to
|
| /netbsd/src/external/ibm-public/postfix/dist/ |
| D | TLS_CHANGES | 1169 The site shall be contacted, they should update.
|
| /netbsd/src/external/gpl2/xcvs/dist/doc/ |
| D | cvsclient.texi | 1523 servers contacted as a result of a @code{Redirect} response. This can be
|
| /netbsd/src/crypto/external/bsd/netpgp/dist/ref/ |
| D | rfc2440.txt | 3425 The working group can be contacted via the current chair:
|
| D | draft-ietf-openpgp-rfc2440bis-12.txt | 3801 The working group can be contacted via the current chair:
|
| D | draft-ietf-openpgp-rfc2440bis-12-ben.txt | 3785 The working group can be contacted via the current chair:
|
| D | draft-ietf-openpgp-rfc2440bis-15.txt | 3838 The working group can be contacted via the current chair:
|
| D | draft-ietf-openpgp-rfc2440bis-14.txt | 3831 The working group can be contacted via the current chair:
|
| D | draft-ietf-openpgp-rfc2440bis-13.txt | 3825 The working group can be contacted via the current chair:
|
| D | rfc4880.txt | 4952 The working group can be contacted via the current chair:
|
| D | draft-ietf-openpgp-rfc2440bis-22.txt | 4466 The working group can be contacted via the current chair:
|
12