Home
last modified time | relevance | path

Searched refs:we (Results 1 – 25 of 1923) sorted by relevance

12345678910>>...77

/src/lib/libc/tests/gen/
H A Dwordexp_test.c57 wordexp_t we; in ATF_TC_BODY() local
67 r = wordexp("hello world", &we, 0); in ATF_TC_BODY()
69 ATF_REQUIRE(we.we_wordc == 2); in ATF_TC_BODY()
70 ATF_REQUIRE(strcmp(we.we_wordv[0], "hello") == 0); in ATF_TC_BODY()
71 ATF_REQUIRE(strcmp(we.we_wordv[1], "world") == 0); in ATF_TC_BODY()
72 ATF_REQUIRE(we.we_wordv[2] == NULL); in ATF_TC_BODY()
73 wordfree(&we); in ATF_TC_BODY()
80 wordexp_t we; in ATF_TC_BODY() local
86 r = wordexp(longdata, &we, 0); in ATF_TC_BODY()
88 ATF_REQUIRE(we.we_wordc == 10000); in ATF_TC_BODY()
[all …]
/src/lib/libc/gen/
H A Dwordexp.c55 wordexp(const char * __restrict words, wordexp_t * __restrict we, int flags) in wordexp() argument
60 wordfree(we); in wordexp()
62 we->we_wordc = 0; in wordexp()
63 we->we_wordv = NULL; in wordexp()
64 we->we_strings = NULL; in wordexp()
65 we->we_nbytes = 0; in wordexp()
68 wordfree(we); in wordexp()
71 if ((error = we_askshell(words, we, flags)) != 0) { in wordexp()
72 wordfree(we); in wordexp()
121 we_askshell(const char *words, wordexp_t *we, int flags) in we_askshell() argument
[all …]
/src/usr.sbin/rwhod/
H A Drwhod.c409 struct whoent *we; in receiver_process() local
418 we = wd.wd_we; in receiver_process()
420 we->we_idle = ntohl(we->we_idle); in receiver_process()
421 we->we_utmp.out_time = in receiver_process()
422 ntohl(we->we_utmp.out_time); in receiver_process()
423 we++; in receiver_process()
447 struct whoent *we, *wend; in sender_process() local
451 we = mywd.wd_we; in sender_process()
458 while ((ut = getutxent()) != NULL && we < wend) { in sender_process()
461 strncpy(we->we_utmp.out_line, ut->ut_line, in sender_process()
[all …]
/src/crypto/openssl/doc/man7/
H A Dossl-guide-tls-client-block.pod24 For example, this can happen if we have sent our request, but we are still
48 L<SSL_CTX_new_ex(3)> if we want to associate the B<SSL_CTX> with a particular
57 * Create an SSL_CTX which we can use to create SSL objects from. We
58 * want an SSL_CTX for creating clients so we use TLS_client_method()
67 Since we are writing a client we must ensure that we verify the server's
84 default store so we call L<SSL_CTX_set_default_verify_paths(3)>.
92 We would also like to restrict the TLS versions that we are willing to accept to
106 That is all the setup that we need to do for the B<SSL_CTX>, so next we need to
108 we might expect to be creating more than one TLS connection over time. In that
109 case we would expect to reuse the B<SSL_CTX> that we already created each time.
[all …]
H A Dossl-guide-tls-client-non-block.pod19 blocking TLS client. On this page we will amend that demo code so that it
27 As we saw in the previous example a blocking socket is one which waits (blocks)
44 L<ossl-guide-tls-client-block(7)> page we assume that you are familiar with it
45 and we only explain how this example differs.
67 we want to read or write to the socket, but we are currently unable to. In fact
82 In this demo application we will create a helper function which simulates doing
124 In this example we are using the C<select> function because it is very simple
130 while waiting for the socket state to change. But we don't use that timeout
138 connection has failed), or non-fatal (for example because we are trying to read
169 In our demo application we will write a function to handle these errors from
[all …]
H A Dossl-guide-quic-client-block.pod29 understanding of UDP/IP and sockets. The example code that we build in this
32 this one will be discussed so we also assume that you have run through and
46 In the TLS tutorial (L<ossl-guide-tls-client-block(7)>) we created an B<SSL_CTX>
53 client. This is done in the same way as before except that we use a different
60 mode", see L<ossl-guide-quic-introduction(7)>). For this tutorial we will be
61 using L<OSSL_QUIC_client_method(3)> because we will not be leaving the QUIC
65 * Create an SSL_CTX which we can use to create SSL objects from. We
66 * want an SSL_CTX for creating clients so we use OSSL_QUIC_client_method()
75 The other setup steps that we applied to the B<SSL_CTX> for TLS also apply to
76 QUIC except for restricting the TLS versions that we are willing to accept. The
[all …]
H A Dossl-guide-quic-client-non-block.pod19 blocking QUIC client. On this page we will amend that demo code so that it
27 As we saw in the previous example an OpenSSL QUIC application always uses a
46 L<ossl-guide-quic-client-block(7)> page we assume that you are familiar with it
47 and we only explain how this example differs.
52 we want to read or write to the B<SSL> object but we are currently unable to.
67 In this demo application we will create a helper function which simulates doing
87 * Find out if we would like to write to the socket, or read from it (or
129 application works. With a TLS application if we try to read or write something
130 to the B<SSL> object and we get a "retry" response (B<SSL_ERROR_WANT_READ> or
131 B<SSL_ERROR_WANT_WRITE>) then we can assume that is because OpenSSL attempted to
[all …]
/src/contrib/tcpdump/
H A Dconfigure.ac24 # Try to enable as many C99 features as we can.
25 # At minimum, we want C++/C99-style // comments.
81 # Do we have pkg-config?
86 # Do we have the brew command from Homebrew?
100 # OK, we found smi.h. Do we have libsmi with smiInit?
105 # OK, we have libsmi with smiInit. Can we use it?
255 # All of the ones we check for must be available in order to enable
258 # XXX - do we need to check for all of them, or are there some that, if
263 # First, make sure we have the required header.
268 # We do; now make sure we have the required functions.
[all …]
H A DCMakeLists.txt3 # We need 3.12 or later, so that we can set policy CMP0074; see
21 # otherwise, require 3.10, so we don't get messages warning
89 # If, for whatever reason, directories in which we search for external
91 # added to the executable's rpath in the build process, we most
141 # Show the bit width for which we're compiling.
145 # libraries that we might use (looking at *you*, Oracle Studio!).
158 # there are two separate .pc files, so if we're doing a 32-bit build we
159 # should make sure we look in /usr/lib/pkgconfig for .pc files and if
160 # we're doing a 64-bit build we should make sure we look in
166 # as an argument, so we set a variable and then use set() to set
[all …]
/src/contrib/jemalloc/doc_internal/
H A DPROFILING_INTERNALS.md9 …we need to walk up the stack to get a stack trace. On top of that, we need to allocate storage to …
12 …0.1145/23002.23003)]), if we can orchestrate our algorithm so that many of our `coinflip` calls sh…
13 …inflip that comes up heads, rather than once per (logical) coinflip. Since we expect to sample rel…
16 …am memory. "Small" and "large" are necessarily sort of fuzzy terms, but if we define "small" as "a…
19 Suppose we have a sampling strategy that meets the following criteria:
28 …tions are fixed; the random variables are the sampling decisions), so taking the expectation we get
32 This is of course $\sum_i S_i$, as we want (and, a similar calculation could be done for allocation…
33 This is a fairly general strategy; note that while we require that sampling decisions be independen…
58 Because of the desire to avoid the fast-path costs, we'd like to use our Bernoulli trick if possibl…
61 …et us use our Bernoulli-via-Geometric trick. Using the formula from above, we can compute the vari…
[all …]
/src/crypto/openssl/doc/designs/quic-design/
H A Ddgram-api.md28 - We do not have to expose functionality which we cannot guarantee
29 we can support on all platforms (for example, arbitrary control messages).
35 - For OSes which do not support `sendmmsg`, we emulate it using repeated
36 calls to `sendmsg`. For OSes which do not support `sendmsg`, we emulate it
65 - The only way we could emulate iovecs on platforms which don't support
78 - Even if we did support iovecs, we would have to impose a limit
79 on the number of iovecs supported, because we translate from our own
187 an equivalent structure. The former has the advantage that we can just pass the
190 Note that in `BIO_mem_dgram` we will have to process and therefore understand
191 the contents of `struct mmsghdr` ourselves. Therefore, initially we define a
[all …]
H A Dquic-connID-retire.md12 * possibly increase the number of CIDs we permit (from 2)
39 When a remote asks to retire a connection ID (RETIRE_CONNECTION_ID) we have to:
45 * Should respond with a NEW_CONNECTION_ID frame if we are low on CIDs
52 However, see above. Suggest we accept either.
54 When we want to retire one (or more) connection IDs we have to:
64 * routes we've retired until they are acked as being retired (uint64_t max CID)
65 * routes our peer has retired don't need tracking, we can remove immediately
66 * retired routes where we've outstanding data to send will have that data
/src/tests/sys/cddl/zfs/tests/cli_root/zpool_upgrade/
H A Dzpool_upgrade.cfg32 # We need to determine which version of ZFS we're running on, so as to
33 # work out which types of pool we should be able to upgrade on this
173 # This statement builds up a list of configurations we should be able to
174 # upgrade, for each pool version. Once we've built this variable, we'll
178 # we should be able to upgrade pools of version 1
183 # we should be able to upgrade pools of version 1 & 2
188 # we should be able to upgrade pools of version 1, 2 & 3
194 # we should be able to upgrade pools of version 1, 2, 3 & 4
200 # we should be able to upgrade pools up to version 5
206 # we should be able to upgrade pools up to version 6
[all …]
/src/contrib/libpcap/
H A Dconfigure.ac28 # for flags required for the platform for which we're building (and
34 # LIBS: inherited from the environment; we add libraries required by
38 # we're finished doing configuration tests for the modules.
64 # or libpcap.pc, as, in all platforms on which we run, if a dynamic
139 dnl include <sys/ioccom.h>, and we were to drop support for older
142 dnl in "aclocal.m4" uses it, so we would still have to test for it
143 dnl and set "HAVE_SYS_IOCCOM_H" if we have it, otherwise
150 # Check whether the platform for which we're compiling requires extra
151 # defines and libraries. If so, add them to CFLAGS and LIBS, as we want
175 # We have strerror_r; if we define _GNU_SOURCE, is it a
[all …]
H A DCMakeLists.txt3 # We need 3.12 or later, so that we can set policy CMP0074; see
21 # otherwise, require 3.10, so we don't get messages warning
36 # neither do we with autotools; don't do so with CMake, either, and
120 # shipping a pre-built shared library cache, at least), and we do the
154 # system library, which we do *NOT* want to put in our libpcap.pc and
157 # So we just run pkg-config ourselves, so that we get its output
181 # package for it to find. XXX - what do we do here?
203 # package for it to find. XXX - what do we do here?
233 # be CMAKE_PLATFORM_IMPLICIT_LINK_DIRECTORIES, so that's what we use
234 # when we're trying to construct a -L argument, for insertion into
[all …]
/src/sys/contrib/device-tree/Bindings/pinctrl/
H A Dsprd,pinctrl.txt12 to choose one function (like: UART0) for which system, since we
15 There are too much various configuration that we can not list all
16 of them, so we can not make every Spreadtrum-special configuration
18 global configuration in future. Then we add one "sprd,control" to
19 set these various global control configuration, and we need use
22 Moreover we recognise every fields comprising one bit or several
23 bits in one global control register as one pin, thus we should
32 Now we have 4 systems for sleep mode on SC9860 SoC: AP system,
42 In some situation we need set the pin sleep mode and pin sleep related
45 sleep mode. For example, if we set the pin sleep mode as PUBCP_SLEEP
[all …]
/src/contrib/ntp/sntp/m4/
H A Dntp_problemtests.m45 dnl While we're in the initial phase of the deployment of the test
6 dnl framework, sometimes we may need to disable these tests.
8 dnl This is where we do that.
16 AC_MSG_CHECKING([if we want to enable tests with undiagnosed problems])
28 AC_MSG_CHECKING([if we can run test-ntp_restrict])
43 AC_MSG_CHECKING([if we can run test-ntp_scanner])
57 AC_MSG_CHECKING([if we can run test-ntp_signd])
H A Dsntp_problemtests.m45 dnl While we're in the initial phase of the deployment of the test
6 dnl framework, sometimes we may need to disable these tests.
8 dnl This is where we do that.
16 AC_MSG_CHECKING([if we want to enable tests with undiagnosed problems])
28 AC_MSG_CHECKING([if we can run test-kodDatabase])
37 AC_MSG_CHECKING([if we can run test-kodFile])
/src/contrib/tcsh/
H A Dtc.func.c1139 struct wordent *we, *args; in rmstar() local
1154 we = cp->next; in rmstar()
1155 while (*we->word == ';' && we != cp) in rmstar()
1156 we = we->next; in rmstar()
1159 while (we != cp) { in rmstar()
1160 Char *cmd = we->word; in rmstar()
1168 args = we->next; in rmstar()
1191 for (tmp = we; in rmstar()
1209 we = tmp; in rmstar()
1215 for (we = we->next; in rmstar()
[all …]
/src/contrib/llvm-project/clang/lib/Headers/openmp_wrappers/
H A Dcomplex37 // If we are compiling against libc++, the macro _LIBCPP_STD_VER should be set
38 // after including <cmath> above. Since the complex header we use is a
39 // simplified version of the libc++, we don't need it in this case. If we
40 // compile against libstdc++, or any other standard library, we will overload
41 // the (hopefully template) functions in the <complex> header with the ones we
43 // arithmetic and calls to non-complex functions, all of which we can then
/src/contrib/tcpdump/cmake/Modules/
H A DFindPCAP.cmake75 # is a WinPcap DLL, but we'd prefer an Npcap DLL (we should
76 # work with either one if we're configured against WinPcap,
77 # and we'll probably require Npcap if we're configured against
84 # Unfortunately, Windows has no notion of an rpath, so we can't
86 # what we need to do is to link wpcap as a delay-load DLL and
97 # Delay-loading libraries means we need to link with delayimp.lib.
105 # See whether we were handed a QUIET argument, so we can pass it on
121 # *If* we were to require CMake 3.1 or later on UN*X,
123 # we're not doing that, in case somebody's building with
128 # If we ever set a minimum of 3.1 or later on UN*X, we should
[all …]
/src/share/examples/netgraph/
H A Dngctl6 # What we will do here create a divert(4) tap. This simply dumps
46 # Note that we used ngctl's ``name'' command to do this. However,
52 # Here we are using the ASCII <-> binary control message conversion
53 # routines. ngctl does this for us automatically when we use the
65 # That is why we can specify the struct sockaddr argument to the
66 # ``bind'' command as ``inet/192.168.1.1'' (since we didn't specify
78 # types when parsing. Now since we didn't ask for a specific port
79 # number, we need to do a ``getname'' to see what port number we got:
85 # As soon as we sent the message, we got back a response. Here
90 # us in its ASCII form. In this case, what we get back is a struct
[all …]
/src/lib/libsecureboot/
H A DREADME.rst15 Within Juniper we use signing servers, which apart from signing things
55 The ``keyID`` we want later will be the last 8 octets
57 This is what we will use for looking up the key.
66 The public key ``ACA72B4719FD2523.pub.asc`` is what we want to
69 we want the trust anchor in a file named ``t*.asc``
97 All we need for this library is a copy of the PEM encoded root CA
107 For Junos we currently use EC DSA signatures with file extension
110 This was the first signature method we used with the remote signing
113 So for Junos we define VE_ECDSA_HASH_AGAIN which causes ``verify_ec``
116 Later I added a FakeHash class to the signing server so we could
[all …]
/src/lib/libefivar/
H A DFreeBSD-update1 For the printing and parsing functionality, we use the Tianocore routines
13 a much better match for plain narrow characters on FreeBSD. So we pretend that
16 Next, we have have to convert the Unicode printf that this code expects to
18 string." so we mechanically convert them. Once we've done that we can compare
19 efivar-dp-*.c to its source to see what's changed. Because we go through this
33 is relatively easy since we map all the UCS-2 routines to simple char *
/src/crypto/heimdal/appl/telnet/
H A Dtelnet.state15 variables. When we are the originator, we can either make the
17 the option is denied we need to change things back) or when
28 * if we are doing so at request initiation
58 * if we are doing so at request acknowledgment
78 will still work. Being conservative in what we send, we have the
79 if() statement in, but we expect the other side to generate the

12345678910>>...77