| /freebsd/contrib/libpcap/ |
| H A D | pcap-tstamp.manmisc.in | 31 done, there are several reasons why it might not precisely represent the
35 receives the packet, the networking stack might not see the packet until
37 networking device driver to poll for packets, and the time stamp might
39 code in the networking stack, so there might be a significant delay
43 the timer used to generate the time stamps might have low resolution,
44 for example, it might be a timer updated once per host operating system
48 a high-resolution timer might use a counter that runs at a rate
49 dependent on the processor clock speed, and that clock speed might be
50 adjusted upwards or downwards over time and the timer might not be able
53 the host operating system's clock might be adjusted over time to match a
[all …]
|
| H A D | pcap_stats.3pcap | 64 might count packets whether they passed any filter set with
66 or not, or it might count only packets that pass the filter.
67 It also might, or might not, count packets dropped because there was no
77 might, or might not, count packets not yet read from the operating
80 might, or might not, be implemented; if it's zero, that might mean that
81 no packets were dropped by the interface, or it might mean that the
|
| H A D | pcap_inject.3pcap | 43 might not have permission to send packets on it, or it might not support
49 Note also that some devices might not support sending packets.
52 sent might not be the same as the link-layer header of the packet
56 address, might be changed to be the address assigned to the interface on
59 platforms might change the link-layer type field to whatever value
|
| H A D | pcap.3pcap.in | 190 associated. It might also supply only data frames, not management or
191 control frames, and might not provide the 802.11 header or radio
196 receives, with 802.11 headers, and might supply a pseudo-header with
199 Note that in monitor mode the adapter might disassociate from the
215 arrives, and might have to make one or more calls to the operating
352 On BSDs with a devfs (this includes macOS), this might involve more
354 or permissions on the BPF devices - it might involve configuring devfs
356 if the system even supports that; if it doesn't support that, you might
619 giving the length of the packet, in bytes (which might be more than the
686 wait might, or might not, terminate even if no packets are available;
|
| /freebsd/share/examples/ipfilter/rules/ |
| H A D | nat-setup | 10 For example, your internal interface might have an IP# of 10.1.1.1 and be
11 connected to your ethernet, whilst your external interface might be a PPP
14 Thus your network might look like this:
39 For an N:1 situation, you might have:
49 Or if you wanted to allocate subnets to each IP#, you might do:
68 in the 10.1.2.0/24 subnet from using NAT, you might use the following rule
|
| /freebsd/contrib/llvm-project/openmp/runtime/src/ |
| H A D | ompd-specific.cpp | 119 we might want to use a separate object file? */ in ompd_dll_locations_valid()
125 we might want to use a separate object file? */ in ompd_bp_parallel_begin()
130 we might want to use a separate object file? */ in ompd_bp_parallel_end()
135 we might want to use a separate object file? */ in ompd_bp_task_begin()
140 we might want to use a separate object file? */ in ompd_bp_task_end()
145 we might want to use a separate object file? */ in ompd_bp_thread_begin()
150 we might want to use a separate object file? */ in ompd_bp_thread_end()
|
| /freebsd/contrib/sendmail/libsm/ |
| H A D | assert.html | 144 For example, you might want to enable SM_REQUIRE checking
173 For example, it might require an entire statement block
291 There are several reasons why a program might be terminated unexpectedly:
292 the system might crash, the program might receive a signal 9,
293 the program might be terminated by a memory fault (possibly as a
295 might detect a logic bug and terminate itself. Note that executing
302 that the program is handling might cause more harm than good: they
303 might cause information to be corrupted or lost.
335 or no cleanup and then dies. A bug might be detected in several ways:
336 the process might dereference a NULL pointer, receive a signal 11,
[all …]
|
| H A D | exc.html | 32 might need to know about an error by a single integer.
162 which might be an error condition like "out of memory", or might be
274 For example, you might want to handle an end-of-file exception
280 /* code that might raise end-of-file, or some other exception */
296 to describe everything that an error handler might want to know about
334 exception handler might want to discriminate.
352 (It might be useful to define subclasses of this category,
369 of a call to malloc, you might corrupt the heap.
588 ... code that might raise an exception ...
598 an existing package that works this way. In this case, it might
[all …]
|
| /freebsd/crypto/heimdal/lib/roken/ |
| H A D | missing | 64 you modified \`acinclude.m4' or \`configure.in'. You might want
73 you modified \`configure.in'. You might want to install the
82 you modified \`acconfig.h' or \`configure.in'. You might want
102 You might want to install the \`Automake' and \`Perl' packages.
167 call might also be the consequence of using a buggy \`make' (AIX,
168 DU, IRIX). You might want to install the \`Texinfo' package or
181 system. You might have modified some files without having the
|
| /freebsd/contrib/llvm-project/llvm/lib/Transforms/Scalar/ |
| H A D | WarnMissedTransforms.cpp | 33 "requested transformation; the transformation might be disabled or " in warnAboutLeftoverTransformations()
44 "the requested transformation; the transformation might be disabled " in warnAboutLeftoverTransformations()
61 "requested transformation; the transformation might be disabled " in warnAboutLeftoverTransformations()
69 "requested transformation; the transformation might be disabled " in warnAboutLeftoverTransformations()
80 "requested transformation; the transformation might be disabled or " in warnAboutLeftoverTransformations()
|
| /freebsd/share/man/man9/ |
| H A D | atomic.9 | 153 By default, a thread's accesses to different memory locations might not be
157 To optimize the program's execution, both the compiler and processor might
165 kernel, might observe the reordering.
167 threads, arbitrary reordering might result in the incorrect execution of the
169 To constrain the reordering that both the compiler and processor might perform
225 Other threads might observe these stores in a different order.
315 However, on some architectures, cache coherence might not be enabled on all
368 might also fail for several reasons, most important of which
|
| /freebsd/share/doc/psd/15.yacc/ |
| H A D | ss7 | 53 in effect, it suggests places where errors are expected, and recovery might take place.
73 scan ahead, looking for three tokens that might legally follow
80 These actions might attempt to reinitialize tables, reclaim symbol table space, etc.
95 A possible error rule might be
129 error recovery action might
|
| /freebsd/contrib/llvm-project/libcxx/include/__math/ |
| H A D | hypot.h | 55 // The naive implementation might over-/underflow which is why this implementation is more involved:
56 // If the square of an argument might run into issues, we scale the arguments appropriately.
60 // Factors needed to determine if over-/underflow might happen in __hypot()
68 if (__max_abs > __overflow_threshold) { // x*x + y*y + z*z might overflow in __hypot()
70 } else if (__max_abs < 1 / __overflow_threshold) { // x*x + y*y + z*z might underflow in __hypot()
|
| /freebsd/contrib/llvm-project/lldb/bindings/interface/ |
| H A D | SBModuleSpecDocstrings.i | 6 platform since we might be doing remote debugging.
18 remote debugging might mention a file '/usr/lib/liba.dylib'
19 which might be locally downloaded and cached. In this case the
|
| /freebsd/contrib/llvm-project/lldb/include/lldb/Target/ |
| H A D | TraceCursor.h | 73 /// As the trace might be empty or the cursor might have reached the end of the
133 /// trace might be needed, for which each instruction requires a unique
134 /// identifier within its thread trace. For example, a tool might want to
149 /// instruction might be encoded by the plug-in in a way that hides its actual
248 /// This call might not be O(1), so it's suggested to invoke this method
259 /// This call might not be O(1), so it's suggested to invoke this method
277 /// different trace technologies might have different values for this,
|
| /freebsd/crypto/heimdal/ |
| H A D | missing | 153 you modified \`acinclude.m4' or \`${configure_ac}'. You might want
162 you modified \`${configure_ac}'. You might want to install the
171 you modified \`acconfig.h' or \`${configure_ac}'. You might want
191 You might want to install the \`Automake' and \`Perl' packages.
201 You might have modified some files without having the
297 call might also be the consequence of using a buggy \`make' (AIX,
298 DU, IRIX). You might want to install the \`Texinfo' package or
359 You might have modified some files without having the
|
| /freebsd/share/man/man3/ |
| H A D | pthread_signals_block_np.3 | 49 might abort sleep and return
61 An example use of these function might be the construction of the CPU
68 to establish critical section might be much slower, because
|
| /freebsd/lib/libsys/ |
| H A D | sigfastblock.2 | 57 A thread might register a
73 which might be set or cleared by kernel at arbitrary moments.
80 If a signal would be delivered when unmasked, kernel might set the
88 Otherwise, signals delivery might be postponed.
|
| /freebsd/share/man/man8/ |
| H A D | diskless.8 | 286 For example, the file might contain:
291 might contain:
362 you might wish to remove unneeded files from the memory file system.
364 if the server has a firewall but you do not, you might wish
403 Finally, it might be convenient to use a
486 The process might not handle all cases.
|
| /freebsd/sys/contrib/device-tree/Bindings/sound/ |
| H A D | cs42l42.txt | 32 debounce, the tip sense pin might be noisy on a plug event.
44 With no debounce, the tip sense pin might be noisy on an unplug event.
77 hardware setups, a designer might want to tweak this. This is an array of
90 with CTIA headset type. For different hardware setups, a designer might
|
| /freebsd/contrib/openbsm/config/ |
| H A D | missing | 162 echo "You might have modified some maintainer files that require"
185 echo "You might want to install the Texinfo package:"
187 echo "The spurious makeinfo call might also be the consequence of"
188 echo "using a buggy 'make' (AIX, DU, IRIX), in which case you might"
193 echo "You might have modified some files without having the proper"
|
| /freebsd/contrib/ntp/sntp/libevent/ |
| H A D | missing | 162 echo "You might have modified some maintainer files that require"
185 echo "You might want to install the Texinfo package:"
187 echo "The spurious makeinfo call might also be the consequence of"
188 echo "using a buggy 'make' (AIX, DU, IRIX), in which case you might"
193 echo "You might have modified some files without having the proper"
|
| /freebsd/contrib/ntp/sntp/libevent/build-aux/ |
| H A D | missing | 162 echo "You might have modified some maintainer files that require"
185 echo "You might want to install the Texinfo package:"
187 echo "The spurious makeinfo call might also be the consequence of"
188 echo "using a buggy 'make' (AIX, DU, IRIX), in which case you might"
193 echo "You might have modified some files without having the proper"
|
| /freebsd/contrib/file/ |
| H A D | missing | 162 echo "You might have modified some maintainer files that require"
185 echo "You might want to install the Texinfo package:"
187 echo "The spurious makeinfo call might also be the consequence of"
188 echo "using a buggy 'make' (AIX, DU, IRIX), in which case you might"
193 echo "You might have modified some files without having the proper"
|
| /freebsd/contrib/libevent/build-aux/ |
| H A D | missing | 162 echo "You might have modified some maintainer files that require"
185 echo "You might want to install the Texinfo package:"
187 echo "The spurious makeinfo call might also be the consequence of"
188 echo "using a buggy 'make' (AIX, DU, IRIX), in which case you might"
193 echo "You might have modified some files without having the proper"
|