Lines Matching refs:a
9 such a case, a process often uses multiple child processes to achieve tasks
15 advantage of multiple cores in modern computers. In a multi-threaded program
19 running an event loop, and each process getting assigned to a separate CPU
25 The simplest case is when you simply want to launch a process and know when it
37 ``options`` is implicitly initialized with zeros since it is a global
38 variable. If you change ``options`` to a local variable, remember to
44 ``uv_process_options_t``. To simply launch a process, you need to set only the
81 ``uv_process_options_t.env`` is a null-terminated array of strings, each of the
88 Setting ``uv_process_options_t.flags`` to a bitwise OR of the following flags,
99 * ``UV_PROCESS_DETACHED`` - Starts the child process in a new session, which
141 a handle and associate it with a loop. To listen for particular signals on
145 stop watching. Here is a small example demonstrating the various possibilities:
165 safely saved before termination, simply by every loop adding a watcher for
174 applications launches a sub-command and you want any errors to go in the log
254 is great. Just be warned that creating processes is a costly task.
261 A parent and child can have one or two way communication over a pipe created by
262 settings ``uv_stdio_container_t.flags`` to a bit-wise combination of
274 Domain Socket`_, or derived from `mkfifo(1)`_, or it could actually be a
275 `pipe(7)`_. When ``uv_spawn`` initializes a ``uv_pipe_t`` due to the
276 `UV_CREATE_PIPE` flag, it opts for creating a `socketpair(2)`_.
291 Since domain sockets [#]_ can have a well known name and a location in the
294 notification. Various applications can then react when a contact comes online
295 or new hardware is detected. The MySQL server also runs a domain socket on
300 When using domain sockets, a client-server pattern is usually followed with the
317 A client which wants to connect to a domain socket will use::
322 point to a valid file (e.g. ``/tmp/echo.sock``). On Windows, ``name`` follows a
331 between processes by sending them over a domain socket. This allows processes
337 clients to worker processes in a round-robin fashion. This program is a bit
365 First we call ``uv_pipe_pending_count()`` to ensure that a handle is available
369 ``accept`` traditionally does is get a file descriptor (the client) from
374 Turning now to the master, let's take a look at how the workers are launched to
397 a readable pipe (from the point of view of the child). Everything is
412 The ``uv_write2`` call handles all the abstraction and it is simply a matter of
416 Thanks to Kyle for `pointing out`_ that ``uv_write2()`` requires a non-empty
