Home
last modified time | relevance | path

Searched refs:follow (Results 1 – 25 of 328) sorted by relevance

12345678910>>...14

/NextBSD/sys/cddl/compat/opensolaris/kern/
HDopensolaris_lookup.c38 lookupname(char *dirname, enum uio_seg seg, enum symfollow follow, in lookupname() argument
42 return (lookupnameat(dirname, seg, follow, dirvpp, compvpp, NULL)); in lookupname()
46 lookupnameat(char *dirname, enum uio_seg seg, enum symfollow follow, in lookupnameat() argument
57 NDINIT_ATVP(&nd, LOOKUP, LOCKLEAF | follow, seg, dirname, in lookupnameat()
/NextBSD/contrib/binutils/bfd/
HDgenlink.h59 #define _bfd_generic_link_hash_lookup(table, string, create, copy, follow) \ argument
61 bfd_link_hash_lookup (&(table)->root, (string), (create), (copy), (follow)))
HDlibxcoff.h104 #define xcoff_link_hash_lookup(table, string, create, copy, follow) \ argument
107 (follow)))
HDlibcoff-in.h283 #define coff_link_hash_lookup(table, string, create, copy, follow) \ argument
286 (copy), (follow)))
/NextBSD/usr.bin/indent/
HDio.c192 char *follow = p; in dump_line() local
194 while (follow < e_com) { in dump_line()
195 switch (*follow) { in dump_line()
203 putc(*follow, output); in dump_line()
205 follow++; in dump_line()
/NextBSD/cddl/contrib/dtracetoolkit/Examples/
HDdtruss_example.txt15 -f # follow children
24 dtruss -f test.sh # run test.sh and follow children
100 Now we try follow mode "-f". The test program does run several hundred
/NextBSD/contrib/ldns/
HDdnssec_zone.c275 bool follow, in ldns_dnssec_rrsets_print_soa_fmt() argument
293 if (follow && rrsets->next) { in ldns_dnssec_rrsets_print_soa_fmt()
295 rrsets->next, follow, show_soa); in ldns_dnssec_rrsets_print_soa_fmt()
304 bool follow) in ldns_dnssec_rrsets_print_fmt() argument
306 ldns_dnssec_rrsets_print_soa_fmt(out, fmt, rrsets, follow, true); in ldns_dnssec_rrsets_print_fmt()
310 ldns_dnssec_rrsets_print(FILE *out, ldns_dnssec_rrsets *rrsets, bool follow) in ldns_dnssec_rrsets_print() argument
313 rrsets, follow); in ldns_dnssec_rrsets_print()
/NextBSD/contrib/ldns/ldns/
HDdnssec_zone.h215 bool follow);
228 bool follow);
/NextBSD/usr.sbin/trpt/
HDtrpt.c90 static int aflag, kflag, memf, follow, sflag, tflag; variable
114 ++follow; in main()
282 done: if (follow) {
/NextBSD/crypto/openssl/crypto/bf/
HDVERSION1 The version numbers will follow my SSL implementation
/NextBSD/contrib/one-true-awk/
HDb.c377 follow(v); /* computes setvec and setcnt */ in cfoll()
445 void follow(Node *v) /* collects leaves that can follow v into setvec */ in follow() function
456 follow(p); in follow()
461 follow(p); in follow()
467 follow(p); in follow()
471 follow(p); in follow()
/NextBSD/contrib/bzip2/
HDwords22 Checking test results. If any of the four "cmp"s which follow
/NextBSD/contrib/tcsh/nls/russian/
HDset911 8 Something must follow: %c\n
/NextBSD/contrib/tcsh/nls/ukrainian/
HDset911 8 Something must follow: %c\n
/NextBSD/contrib/tcsh/nls/C/
HDset911 8 Something must follow: %c\n
/NextBSD/tests/
HDREADME23 * The goal for /usr/tests/ (the installed test programs) is to follow
44 and thus don't fit anywhere else in the tree. Consider this to follow
/NextBSD/usr.bin/tail/
HDextern.h59 void follow(file_info_t *, enum STYLE, off_t);
/NextBSD/usr.bin/rpcgen/
HDrpc_util.c169 ptype(const char *prefix, const char *type, int follow) in ptype() argument
183 f_print(fout, "%s ", follow ? fixtype(type) : type); in ptype()
HDrpc_util.h176 void ptype(const char *prefix, const char *type, int follow);
/NextBSD/contrib/pjdfstest/
HDFREEBSD-upgrade6 branches and you are supposed to follow those:
/NextBSD/contrib/netbsd-tests/fs/tmpfs/
HDREADME2 developed. This is why, if you follow the order of tests in the Atffile,
/NextBSD/bin/sh/tests/expansion/
HDplus-minus3.024 # We follow original ash behaviour for quoted ${var+-=?} expansions:
/NextBSD/contrib/ntp/
HDREADME.leapsmear71 e.g. several hours, so that NTP clients can easily follow the clock drift
159 NTP clients can follow the smeared time it doesn't matter at all which
163 Since all clients follow the same smeared time the time difference between
207 is applied too quickly for clients to follow. 86400s (1 day) is a good
240 hours' long. With shorter values clients may not be able to follow the
/NextBSD/contrib/netbsd-tests/
HDFREEBSD-upgrade6 branches and you are supposed to follow those:
/NextBSD/contrib/ofed/management/opensm/doc/
HDopensm-coding-style.txt29 * When writing new code, please try to follow the new Coding style.

12345678910>>...14