Home
last modified time | relevance | path

Searched refs:them (Results 1 – 25 of 1012) sorted by relevance

12345678910>>...41

/NextBSD/crypto/openssl/crypto/bio/
HDbss_conn.c85 struct sockaddr_in them; member
188 memset((char *)&c->them, 0, sizeof(c->them)); in conn_state()
189 c->them.sin_family = AF_INET; in conn_state()
190 c->them.sin_port = htons((unsigned short)c->port); in conn_state()
195 c->them.sin_addr.s_addr = htonl(l); in conn_state()
238 (struct sockaddr *)&c->them, sizeof(c->them)); in conn_state()
308 memset((char *)&ret->them, 0, sizeof(ret->them)); in BIO_CONNECT_new()
/NextBSD/crypto/openssl/apps/
HDs_socket.c247 struct sockaddr_in them; in init_client_ip() local
253 memset((char *)&them, 0, sizeof(them)); in init_client_ip()
254 them.sin_family = AF_INET; in init_client_ip()
255 them.sin_port = htons((unsigned short)port); in init_client_ip()
260 them.sin_addr.s_addr = htonl(addr); in init_client_ip()
283 if (connect(s, (struct sockaddr *)&them, sizeof(them)) == -1) { in init_client_ip()
/NextBSD/lib/libc/db/hash/
HDREADME7 All test programs which need key/data pairs expect them entered
34 Reads the key/data pairs in the file hashtest and writes them
39 Reads key/data pairs from standard in and looks them up
42 Reads key/data pairs from standard in, looks them up
/NextBSD/lib/libc/quad/
HDSymbol.map9 * broken and they expect to see them in libc. glibc exports
10 * them, but they do not appear to be exported in Solaris.
/NextBSD/sys/boot/arm/uboot/
HDhelp.uboot8 Display U-Boot environment variables, or import them into the
9 loader environment (which makes them available in the kernel).
/NextBSD/contrib/llvm/tools/clang/include/clang/Basic/
HDTokenKinds.def671 // handles them.
676 // handles them.
681 // handles them.
686 // handles them.
691 // handles them.
696 // handles them.
701 // handles them.
706 // handles them.
711 // handles them.
716 // handles them.
[all …]
/NextBSD/crypto/openssl/doc/crypto/
HDOpenSSL_add_all_algorithms.pod42 An application does not need to add algorithms to use them explicitly, for example
43 by EVP_sha1(). It just needs to add them if it (or any of the functions it calls)
57 Although the functions do not return error codes it is possible for them to fail.
HDCMS_decrypt.pod43 B<extreme caution> especially in automated gateways as it can leave them
47 example looking them up in a database) and setting them in the CMS structure
/NextBSD/usr.bin/fortune/
HDREADME7 upon reading one of them, edit the Makefile in the subdirectory datfiles,
20 ... on them."
23 people nowadays are casting aside the pietistic attitude that has led them
/NextBSD/crypto/openssh/
HDTODO11 would be best to use them.
38 and order to try them in e.g. "ChallengeResponseAuthentication skey, pam"
53 left to do. HAVE_LOGIN is one of them. Consider NOT looking for
/NextBSD/tools/tools/kdrv/
HDsample.drvinfo26 # optioni386 causes them to be added to i386/conf/options.i386
27 # optionconf causes them to be added to conf/options
/NextBSD/contrib/atf/
HDREADME12 program written with them exposes a consistent user interface.
14 ATF-based test programs rely on a separate runtime engine to execute them.
/NextBSD/contrib/gdb/gdb/config/i386/
HDi386gnu.mh13 # Use our own user stubs for the msg rpcs, so we can make them time out, in
21 # them work correctly for error returns in some cases.
/NextBSD/contrib/gcc/doc/include/
HDfunding.texi23 it from them. So when you compare distributors, judge them partly by
45 contribute little, since someone else would surely do them; difficult
/NextBSD/contrib/ipfilter/
HDSTYLE.TXT3 coding style than it had before. If you submit patches, I expect them to
18 /* then get a result stored in them qualify here. */
/NextBSD/sys/dev/isp/
HDHardware.txt61 to the role you're using them for- otherwise things don't
151 can see them very clearly from 50 feet away.
188 typically have had few problems with them. These are the bare
199 on the JBOD you put them to carry this dual port to the outside
274 want them to- and this makes for a much more reliable, if more expensive,
299 fabric login policy is simplistic (log them in as you find them). If
/NextBSD/sys/boot/i386/pxeldr/
HDpxeldr.S47 .set MEM_ARG_BTX,0xa100 # Where we move them to so the
48 # BTX client can see them
/NextBSD/contrib/ipfilter/ipsd/
HDREADME8 detect all packets going to/through them.
29 done or discourage them.
/NextBSD/contrib/groff/contrib/mom/
HDBUGS43 them (e.g. $COVERTITLE).
310 to have them run 1 line shorter than they should. The problem stems
313 surrounding them to get them to bottom align. Since stylistically,
315 least some running text beneath them in order to make sense of the role
/NextBSD/usr.sbin/cron/doc/
HDREADME41 source, and since I'd love to see them use it, I'll offer some rediculously
42 low license fee just to have them take it. In the unlikely event that they
61 (either put them all in "root"'s crontab, or divide it up
/NextBSD/contrib/tcsh/
HDimake.config15 better to set up new definitions in the Imakefile than to put them
60 want them to be something else. */
/NextBSD/contrib/groff/font/devutf8/
HDNOTES24 this glyph is just too small. We map them to 0x007E instead.
27 this glyph is just too small. We map them to 0x005E instead.
/NextBSD/contrib/subversion/subversion/libsvn_fs_x/
HDTODO9 to make them available to other fsfs code. We need to revisit those
10 function definitions to turn them into a proper API that may be useful
121 packs (10-ish) and later pack them into larger and larger ones.
130 Combine most of them into one or two files (eg uuid|format(|fs-type?),
192 * no fragments should be left but if they are, put them at the end
269 in path names when using them in textual item representations.
/NextBSD/gnu/usr.bin/grep/tests/
HDformatbre.awk43 # skip those magic cookies can't rely on echo to gnerate them
HDformatere.awk44 # skip those magic cookies can't rely on echo to gnerate them

12345678910>>...41