2 * Copyright 2015 Facebook, Inc.
4 * Licensed under the Apache License, Version 2.0 (the "License");
5 * you may not use this file except in compliance with the License.
6 * You may obtain a copy of the License at
8 * http://www.apache.org/licenses/LICENSE-2.0
10 * Unless required by applicable law or agreed to in writing, software
11 * distributed under the License is distributed on an "AS IS" BASIS,
12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 * See the License for the specific language governing permissions and
14 * limitations under the License.
18 * Subprocess library, modeled after Python's subprocess module
19 * (http://docs.python.org/2/library/subprocess.html)
21 * This library defines one class (Subprocess) which represents a child
22 * process. Subprocess has two constructors: one that takes a vector<string>
23 * and executes the given executable without using the shell, and one
24 * that takes a string and executes the given command using the shell.
25 * Subprocess allows you to redirect the child's standard input, standard
26 * output, and standard error to/from child descriptors in the parent,
27 * or to create communication pipes between the child and the parent.
29 * The simplest example is a thread-safe [1] version of the system() library
31 * Subprocess(cmd).wait();
32 * which executes the command using the default shell and waits for it
33 * to complete, returning the exit status.
35 * A thread-safe [1] version of popen() (type="r", to read from the child):
36 * Subprocess proc(cmd, Subprocess::pipeStdout());
37 * // read from proc.stdout()
40 * A thread-safe [1] version of popen() (type="w", to write to the child):
41 * Subprocess proc(cmd, Subprocess::pipeStdin());
42 * // write to proc.stdin()
45 * If you want to redirect both stdin and stdout to pipes, you can, but note
46 * that you're subject to a variety of deadlocks. You'll want to use
47 * nonblocking I/O, like the callback version of communicate().
49 * The string or IOBuf-based variants of communicate() are the simplest way
50 * to communicate with a child via its standard input, standard output, and
51 * standard error. They buffer everything in memory, so they are not great
52 * for large amounts of data (or long-running processes), but they are much
53 * simpler than the callback version.
55 * == A note on thread-safety ==
57 * [1] "thread-safe" refers ONLY to the fact that Subprocess is very careful
58 * to fork in a way that does not cause grief in multithreaded programs.
60 * Caveat: If your system does not have the atomic pipe2 system call, it is
61 * not safe to concurrently call Subprocess from different threads.
62 * Therefore, it is best to have a single thread be responsible for spawning
65 * A particular instances of Subprocess is emphatically **not** thread-safe.
66 * If you need to simultaneously communicate via the pipes, and interact
67 * with the Subprocess state, your best bet is to:
68 * - takeOwnershipOfPipes() to separate the pipe I/O from the subprocess.
69 * - Only interact with the Subprocess from one thread at a time.
71 * The current implementation of communicate() cannot be safely interrupted.
72 * To do so correctly, one would need to use EventFD, or open a dedicated
73 * pipe to be messaged from a different thread -- in particular, kill() will
74 * not do, since a descendant may keep the pipes open indefinitely.
76 * So, once you call communicate(), you must wait for it to return, and not
77 * touch the pipes from other threads. closeParentFd() is emphatically
78 * unsafe to call concurrently, and even sendSignal() is not a good idea.
79 * You can perhaps give the Subprocess's PID to a different thread before
80 * starting communicate(), and use that PID to send a signal without
81 * accessing the Subprocess object. In that case, you will need a mutex
82 * that ensures you don't wait() before you sent said signal. In a
83 * nutshell, don't do this.
85 * In fact, signals are inherently concurrency-unsafe on Unix: if you signal
86 * a PID, while another thread is in waitpid(), the signal may fire either
87 * before or after the process is reaped. This means that your signal can,
88 * in pathological circumstances, be delivered to the wrong process (ouch!).
89 * To avoid this, you should only use non-blocking waits (i.e. poll()), and
90 * make sure to serialize your signals (i.e. kill()) with the waits --
91 * either wait & signal from the same thread, or use a mutex.
93 #ifndef FOLLY_SUBPROCESS_H_
94 #define FOLLY_SUBPROCESS_H_
96 #include <sys/types.h>
108 #include <boost/container/flat_map.hpp>
109 #include <boost/operators.hpp>
111 #include <folly/File.h>
112 #include <folly/FileUtil.h>
113 #include <folly/gen/String.h>
114 #include <folly/io/IOBufQueue.h>
115 #include <folly/MapUtil.h>
116 #include <folly/Portability.h>
117 #include <folly/Range.h>
122 * Class to wrap a process return code.
125 class ProcessReturnCode {
126 friend class Subprocess;
135 // Trivially copyable
136 ProcessReturnCode(const ProcessReturnCode& p) = default;
137 ProcessReturnCode& operator=(const ProcessReturnCode& p) = default;
138 // Non-default move: In order for Subprocess to be movable, the "moved
139 // out" state must not be "running", or ~Subprocess() will abort.
140 ProcessReturnCode(ProcessReturnCode&& p) noexcept;
141 ProcessReturnCode& operator=(ProcessReturnCode&& p) noexcept;
144 * Process state. One of:
145 * NOT_STARTED: process hasn't been started successfully
146 * RUNNING: process is currently running
147 * EXITED: process exited (successfully or not)
148 * KILLED: process was killed by a signal.
153 * Helper wrappers around state().
155 bool notStarted() const { return state() == NOT_STARTED; }
156 bool running() const { return state() == RUNNING; }
157 bool exited() const { return state() == EXITED; }
158 bool killed() const { return state() == KILLED; }
161 * Exit status. Only valid if state() == EXITED; throws otherwise.
163 int exitStatus() const;
166 * Signal that caused the process's termination. Only valid if
167 * state() == KILLED; throws otherwise.
169 int killSignal() const;
172 * Was a core file generated? Only valid if state() == KILLED; throws
175 bool coreDumped() const;
178 * String representation; one of
181 * "exited with status <status>"
182 * "killed by signal <signal>"
183 * "killed by signal <signal> (core dumped)"
185 std::string str() const;
188 * Helper function to enforce a precondition based on this.
189 * Throws std::logic_error if in an unexpected state.
191 void enforce(State state) const;
193 explicit ProcessReturnCode(int rv) : rawStatus_(rv) { }
194 static constexpr int RV_NOT_STARTED = -2;
195 static constexpr int RV_RUNNING = -1;
201 * Base exception thrown by the Subprocess methods.
203 class SubprocessError : public std::exception {};
206 * Exception thrown by *Checked methods of Subprocess.
208 class CalledProcessError : public SubprocessError {
210 explicit CalledProcessError(ProcessReturnCode rc);
211 ~CalledProcessError() throw() { }
212 const char* what() const throw() FOLLY_OVERRIDE { return what_.c_str(); }
213 ProcessReturnCode returnCode() const { return returnCode_; }
215 ProcessReturnCode returnCode_;
220 * Exception thrown if the subprocess cannot be started.
222 class SubprocessSpawnError : public SubprocessError {
224 SubprocessSpawnError(const char* executable, int errCode, int errnoValue);
225 ~SubprocessSpawnError() throw() {}
226 const char* what() const throw() FOLLY_OVERRIDE { return what_.c_str(); }
227 int errnoValue() const { return errnoValue_; }
239 static const int CLOSE = -1;
240 static const int PIPE = -2;
241 static const int PIPE_IN = -3;
242 static const int PIPE_OUT = -4;
245 * Class representing various options: file descriptor behavior, and
246 * whether to use $PATH for searching for the executable,
248 * By default, we don't use $PATH, file descriptors are closed if
249 * the close-on-exec flag is set (fcntl FD_CLOEXEC) and inherited
252 class Options : private boost::orable<Options> {
253 friend class Subprocess;
255 Options() {} // E.g. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58328
258 * Change action for file descriptor fd.
260 * "action" may be another file descriptor number (dup2()ed before the
261 * child execs), or one of CLOSE, PIPE_IN, and PIPE_OUT.
263 * CLOSE: close the file descriptor in the child
264 * PIPE_IN: open a pipe *from* the child
265 * PIPE_OUT: open a pipe *to* the child
267 * PIPE is a shortcut; same as PIPE_IN for stdin (fd 0), same as
268 * PIPE_OUT for stdout (fd 1) or stderr (fd 2), and an error for
269 * other file descriptors.
271 Options& fd(int fd, int action);
274 * Shortcut to change the action for standard input.
276 Options& stdin(int action) { return fd(STDIN_FILENO, action); }
279 * Shortcut to change the action for standard output.
281 Options& stdout(int action) { return fd(STDOUT_FILENO, action); }
284 * Shortcut to change the action for standard error.
285 * Note that stderr(1) will redirect the standard error to the same
286 * file descriptor as standard output; the equivalent of bash's "2>&1"
288 Options& stderr(int action) { return fd(STDERR_FILENO, action); }
290 Options& pipeStdin() { return fd(STDIN_FILENO, PIPE_IN); }
291 Options& pipeStdout() { return fd(STDOUT_FILENO, PIPE_OUT); }
292 Options& pipeStderr() { return fd(STDERR_FILENO, PIPE_OUT); }
295 * Close all other fds (other than standard input, output, error,
296 * and file descriptors explicitly specified with fd()).
298 * This is potentially slow; it's generally a better idea to
299 * set the close-on-exec flag on all file descriptors that shouldn't
300 * be inherited by the child.
302 * Even with this option set, standard input, output, and error are
303 * not closed; use stdin(CLOSE), stdout(CLOSE), stderr(CLOSE) if you
306 Options& closeOtherFds() { closeOtherFds_ = true; return *this; }
309 * Use the search path ($PATH) when searching for the executable.
311 Options& usePath() { usePath_ = true; return *this; }
314 * Change the child's working directory, after the vfork.
316 Options& chdir(const std::string& dir) { childDir_ = dir; return *this; }
320 * Child will receive a signal when the parent exits.
322 Options& parentDeathSignal(int sig) {
323 parentDeathSignal_ = sig;
329 * Child will be made a process group leader when it starts. Upside: one
330 * can reliably all its kill non-daemonizing descendants. Downside: the
331 * child will not receive Ctrl-C etc during interactive use.
333 Options& processGroupLeader() {
334 processGroupLeader_ = true;
339 * Helpful way to combine Options.
341 Options& operator|=(const Options& other);
344 typedef boost::container::flat_map<int, int> FdMap;
346 bool closeOtherFds_{false};
347 bool usePath_{false};
348 std::string childDir_; // "" keeps the parent's working directory
350 int parentDeathSignal_{0};
352 bool processGroupLeader_{false};
355 static Options pipeStdin() { return Options().stdin(PIPE); }
356 static Options pipeStdout() { return Options().stdout(PIPE); }
357 static Options pipeStderr() { return Options().stderr(PIPE); }
359 // Non-copiable, but movable
360 Subprocess(const Subprocess&) = delete;
361 Subprocess& operator=(const Subprocess&) = delete;
362 Subprocess(Subprocess&&) = default;
363 Subprocess& operator=(Subprocess&&) = default;
366 * Create a subprocess from the given arguments. argv[0] must be listed.
367 * If not-null, executable must be the actual executable
368 * being used (otherwise it's the same as argv[0]).
370 * If env is not-null, it must contain name=value strings to be used
371 * as the child's environment; otherwise, we inherit the environment
372 * from the parent. env must be null if options.usePath is set.
375 const std::vector<std::string>& argv,
376 const Options& options = Options(),
377 const char* executable = nullptr,
378 const std::vector<std::string>* env = nullptr);
382 * Create a subprocess run as a shell command (as shell -c 'command')
384 * The shell to use is taken from the environment variable $SHELL,
385 * or /bin/sh if $SHELL is unset.
388 const std::string& cmd,
389 const Options& options = Options(),
390 const std::vector<std::string>* env = nullptr);
393 //// The methods below only manipulate the process state, and do not
394 //// affect its communication pipes.
398 * Return the child's pid, or -1 if the child wasn't successfully spawned
399 * or has already been wait()ed upon.
404 * Return the child's status (as per wait()) if the process has already
405 * been waited on, -1 if the process is still running, or -2 if the
406 * process hasn't been successfully started. NOTE that this does not call
407 * waitpid() or Subprocess::poll(), but simply returns the status stored
408 * in the Subprocess object.
410 ProcessReturnCode returnCode() const { return returnCode_; }
413 * Poll the child's status and return it, return -1 if the process
414 * is still running. NOTE that it is illegal to call poll again after
415 * poll indicated that the process has terminated, or to call poll on a
416 * process that hasn't been successfully started (the constructor threw an
419 ProcessReturnCode poll();
422 * Poll the child's status. If the process is still running, return false.
423 * Otherwise, return true if the process exited with status 0 (success),
424 * or throw CalledProcessError if the process exited with a non-zero status.
429 * Wait for the process to terminate and return its status.
430 * Similarly to poll, it is illegal to call wait after the process
431 * has already been reaped or if the process has not successfully started.
433 ProcessReturnCode wait();
436 * Wait for the process to terminate, throw if unsuccessful.
441 * Send a signal to the child. Shortcuts for the commonly used Unix
444 void sendSignal(int signal);
445 void terminate() { sendSignal(SIGTERM); }
446 void kill() { sendSignal(SIGKILL); }
449 //// The methods below only affect the process's communication pipes, but
450 //// not its return code or state (they do not poll() or wait()).
454 * Communicate with the child until all pipes to/from the child are closed.
456 * The input buffer is written to the process' stdin pipe, and data is read
457 * from the stdout and stderr pipes. Non-blocking I/O is performed on all
458 * pipes simultaneously to avoid deadlocks.
460 * The stdin pipe will be closed after the full input buffer has been written.
461 * An error will be thrown if a non-empty input buffer is supplied but stdin
462 * was not configured as a pipe.
464 * Returns a pair of buffers containing the data read from stdout and stderr.
465 * If stdout or stderr is not a pipe, an empty IOBuf queue will be returned
466 * for the respective buffer.
468 * Note that communicate() and communicateIOBuf() both return when all
469 * pipes to/from the child are closed; the child might stay alive after
470 * that, so you must still wait().
472 * communicateIOBuf() uses IOBufQueue for buffering (which has the
473 * advantage that it won't try to allocate all data at once), but it does
474 * store the subprocess's entire output in memory before returning.
476 * communicate() uses strings for simplicity.
478 std::pair<IOBufQueue, IOBufQueue> communicateIOBuf(
479 IOBufQueue input = IOBufQueue());
481 std::pair<std::string, std::string> communicate(
482 StringPiece input = StringPiece());
485 * Communicate with the child until all pipes to/from the child are closed.
489 * readCallback(pfd, cfd) will be called whenever there's data available
490 * on any pipe *from* the child (PIPE_OUT). pfd is the file descriptor
491 * in the parent (that you use to read from); cfd is the file descriptor
492 * in the child (used for identifying the stream; 1 = child's standard
493 * output, 2 = child's standard error, etc)
495 * writeCallback(pfd, cfd) will be called whenever a pipe *to* the child is
496 * writable (PIPE_IN). pfd is the file descriptor in the parent (that you
497 * use to write to); cfd is the file descriptor in the child (used for
498 * identifying the stream; 0 = child's standard input, etc)
500 * The read and write callbacks must read from / write to pfd and return
501 * false during normal operation. Return true to tell communicate() to
502 * close the pipe. For readCallback, this might send SIGPIPE to the
503 * child, or make its writes fail with EPIPE, so you should generally
504 * avoid returning true unless you've reached end-of-file.
506 * communicate() returns when all pipes to/from the child are closed; the
507 * child might stay alive after that, so you must still wait().
508 * Conversely, the child may quit long before its pipes are closed, since
509 * its descendants can keep them alive forever.
511 * Most users won't need to use this callback version; the simpler version
512 * of communicate (which buffers data in memory) will probably work fine.
514 * == Things you must get correct ==
516 * 1) You MUST consume all data passed to readCallback (or return true to
517 * close the pipe). Similarly, you MUST write to a writable pipe (or
518 * return true to close the pipe). To do otherwise is an error that can
519 * result in a deadlock. You must do this even for pipes you are not
522 * 2) pfd is nonblocking, so be prepared for read() / write() to return -1
523 * and set errno to EAGAIN (in which case you should return false). Use
524 * readNoInt() from FileUtil.h to handle interrupted reads for you.
526 * 3) Your callbacks MUST NOT call any of the Subprocess methods that
527 * manipulate the pipe FDs. Check the docblocks, but, for example,
528 * neither closeParentFd (return true instead) nor takeOwnershipOfPipes
529 * are safe. Stick to reading/writing from pfd, as appropriate.
533 * 1) See ReadLinesCallback for an easy way to consume the child's output
534 * streams line-by-line (or tokenized by another delimiter).
536 * 2) "Wait until the descendants close the pipes" is usually the behavior
537 * you want, since the descendants may have something to say even if the
538 * immediate child is dead. If you need to be able to force-close all
539 * parent FDs, communicate() will NOT work for you. Do it your own way by
540 * using takeOwnershipOfPipes().
542 * Why not? You can return "true" from your callbacks to sever active
543 * pipes, but inactive ones can remain open indefinitely. It is
544 * impossible to safely close inactive pipes while another thread is
545 * blocked in communicate(). This is BY DESIGN. Racing communicate()'s
546 * read/write callbacks can result in wrong I/O and data corruption. This
547 * class would need internal synchronization and timeouts, a poor and
548 * expensive implementation choice, in order to make closeParentFd()
551 typedef std::function<bool(int, int)> FdCallback;
552 void communicate(FdCallback readCallback, FdCallback writeCallback);
555 * A readCallback for Subprocess::communicate() that helps you consume
556 * lines (or other delimited pieces) from your subprocess's file
557 * descriptors. Use the readLinesCallback() helper to get template
558 * deduction. For example:
560 * auto read_cb = Subprocess::readLinesCallback(
561 * [](int fd, folly::StringPiece s) {
562 * std::cout << fd << " said: " << s;
563 * return false; // Keep reading from the child
566 * subprocess.communicate(
567 * // ReadLinesCallback contains StreamSplitter contains IOBuf, making
568 * // it noncopyable, whereas std::function must be copyable. So, we
569 * // keep the callback in a local, and instead pass a reference.
571 * [](int pdf, int cfd){ return true; } // Don't write to the child
574 * If a file line exceeds maxLineLength, your callback will get some
575 * initial chunks of maxLineLength with no trailing delimiters. The final
576 * chunk of a line is delimiter-terminated iff the delimiter was present
577 * in the input. In particular, the last line in a file always lacks a
578 * delimiter -- so if a file ends on a delimiter, the final line is empty.
580 * Like a regular communicate() callback, your fdLineCb() normally returns
581 * false. It may return true to tell Subprocess to close the underlying
582 * file descriptor. The child process may then receive SIGPIPE or get
583 * EPIPE errors on writes.
585 template <class Callback>
586 class ReadLinesCallback {
588 // Binds an FD to the client-provided FD+line callback
589 struct StreamSplitterCallback {
590 StreamSplitterCallback(Callback& cb, int fd) : cb_(cb), fd_(fd) { }
591 // The return value semantics are inverted vs StreamSplitter
592 bool operator()(StringPiece s) { return !cb_(fd_, s); }
596 typedef gen::StreamSplitter<StreamSplitterCallback> LineSplitter;
598 explicit ReadLinesCallback(
600 uint64_t maxLineLength = 0, // No line length limit by default
601 char delimiter = '\n',
602 uint64_t bufSize = 1024
603 ) : fdLineCb_(std::move(fdLineCb)),
604 maxLineLength_(maxLineLength),
605 delimiter_(delimiter),
608 bool operator()(int pfd, int cfd) {
609 // Make a splitter for this cfd if it doesn't already exist
610 auto it = fdToSplitter_.find(cfd);
611 auto& splitter = (it != fdToSplitter_.end()) ? it->second
612 : fdToSplitter_.emplace(cfd, LineSplitter(
613 delimiter_, StreamSplitterCallback(fdLineCb_, cfd), maxLineLength_
615 // Read as much as we can from this FD
618 ssize_t ret = readNoInt(pfd, buf, bufSize_);
619 if (ret == -1 && errno == EAGAIN) { // No more data for now
622 if (ret == 0) { // Reached end-of-file
623 splitter.flush(); // Ignore return since the file is over anyway
626 if (!splitter(StringPiece(buf, ret))) {
627 return true; // The callback told us to stop
634 const uint64_t maxLineLength_;
635 const char delimiter_;
636 const uint64_t bufSize_;
637 // We lazily make splitters for all cfds that get used.
638 std::unordered_map<int, LineSplitter> fdToSplitter_;
641 // Helper to enable template deduction
642 template <class Callback>
643 static ReadLinesCallback<Callback> readLinesCallback(
645 uint64_t maxLineLength = 0, // No line length limit by default
646 char delimiter = '\n',
647 uint64_t bufSize = 1024) {
648 return ReadLinesCallback<Callback>(
649 std::move(fdLineCb), maxLineLength, delimiter, bufSize
654 * communicate() callbacks can use this to temporarily enable/disable
655 * notifications (callbacks) for a pipe to/from the child. By default,
656 * all are enabled. Useful for "chatty" communication -- you want to
657 * disable write callbacks until you receive the expected message.
659 * Disabling a pipe does not free you from the requirement to consume all
660 * incoming data. Failing to do so will easily create deadlock bugs.
662 * Throws if the childFd is not known.
664 void enableNotifications(int childFd, bool enabled);
667 * Are notifications for one pipe to/from child enabled? Throws if the
668 * childFd is not known.
670 bool notificationsEnabled(int childFd) const;
673 //// The following methods are meant for the cases when communicate() is
674 //// not suitable. You should not need them when you call communicate(),
675 //// and, in fact, it is INHERENTLY UNSAFE to use closeParentFd() or
676 //// takeOwnershipOfPipes() from a communicate() callback.
680 * Close the parent file descriptor given a file descriptor in the child.
681 * DO NOT USE from communicate() callbacks; make them return true instead.
683 void closeParentFd(int childFd);
686 * Set all pipes from / to child to be non-blocking. communicate() does
689 void setAllNonBlocking();
692 * Get parent file descriptor corresponding to the given file descriptor
693 * in the child. Throws if childFd isn't a pipe (PIPE_IN / PIPE_OUT).
694 * Do not close() the returned file descriptor; use closeParentFd, above.
696 int parentFd(int childFd) const {
697 return pipes_[findByChildFd(childFd)].pipe.fd();
699 int stdin() const { return parentFd(0); }
700 int stdout() const { return parentFd(1); }
701 int stderr() const { return parentFd(2); }
704 * The child's pipes are logically separate from the process metadata
705 * (they may even be kept alive by the child's descendants). This call
706 * lets you manage the pipes' lifetime separetely from the lifetime of the
709 * After this call, the Subprocess instance will have no knowledge of
710 * these pipes, and the caller assumes responsibility for managing their
711 * lifetimes. Pro-tip: prefer to explicitly close() the pipes, since
712 * folly::File would otherwise silently suppress I/O errors.
714 * No, you may NOT call this from a communicate() callback.
717 ChildPipe(int fd, folly::File&& ppe) : childFd(fd), pipe(std::move(ppe)) {}
719 folly::File pipe; // Owns the parent FD
721 std::vector<ChildPipe> takeOwnershipOfPipes();
724 static const int RV_RUNNING = ProcessReturnCode::RV_RUNNING;
725 static const int RV_NOT_STARTED = ProcessReturnCode::RV_NOT_STARTED;
727 // spawn() sets up a pipe to read errors from the child,
728 // then calls spawnInternal() to do the bulk of the work. Once
729 // spawnInternal() returns it reads the error pipe to see if the child
730 // encountered any errors.
732 std::unique_ptr<const char*[]> argv,
733 const char* executable,
734 const Options& options,
735 const std::vector<std::string>* env);
737 std::unique_ptr<const char*[]> argv,
738 const char* executable,
740 const std::vector<std::string>* env,
743 // Actions to run in child.
744 // Note that this runs after vfork(), so tread lightly.
745 // Returns 0 on success, or an errno value on failure.
746 int prepareChild(const Options& options,
747 const sigset_t* sigmask,
748 const char* childDir) const;
749 int runChild(const char* executable, char** argv, char** env,
750 const Options& options) const;
753 * Read from the error pipe, and throw SubprocessSpawnError if the child
754 * failed before calling exec().
756 void readChildErrorPipe(int pfd, const char* executable);
758 // Returns an index into pipes_. Throws std::invalid_argument if not found.
759 size_t findByChildFd(const int childFd) const;
763 ProcessReturnCode returnCode_;
766 * Represents a pipe between this process, and the child process (or its
767 * descendant). To interact with these pipes, you can use communicate(),
768 * or use parentFd() and related methods, or separate them from the
769 * Subprocess instance entirely via takeOwnershipOfPipes().
771 struct Pipe : private boost::totally_ordered<Pipe> {
772 folly::File pipe; // Our end of the pipe, wrapped in a File to auto-close.
773 int childFd = -1; // Identifies the pipe: what FD is this in the child?
774 int direction = PIPE_IN; // one of PIPE_IN / PIPE_OUT
775 bool enabled = true; // Are notifications enabled in communicate()?
777 bool operator<(const Pipe& other) const {
778 return childFd < other.childFd;
780 bool operator==(const Pipe& other) const {
781 return childFd == other.childFd;
785 // Populated at process start according to fdActions, empty after
786 // takeOwnershipOfPipes(). Sorted by childFd. Can only have elements
787 // erased, but not inserted, after being populated.
789 // The number of pipes between parent and child is assumed to be small,
790 // so we're happy with a vector here, even if it means linear erase.
791 std::vector<Pipe> pipes_;
794 inline Subprocess::Options& Subprocess::Options::operator|=(
795 const Subprocess::Options& other) {
796 if (this == &other) return *this;
798 for (auto& p : other.fdActions_) {
799 fdActions_[p.first] = p.second;
801 closeOtherFds_ |= other.closeOtherFds_;
802 usePath_ |= other.usePath_;
803 processGroupLeader_ |= other.processGroupLeader_;
809 #endif /* FOLLY_SUBPROCESS_H_ */