1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

//! The `Command` has mostly same API as `std::process::Command` except
//! where is absolutely needed.
//!
//! In addition `Command` contains methods to configure linux namespaces,
//! chroots and more linux stuff.
//!
//! The one prominent exception here is error handling. Since sometimes we
//! have long chains of systemcalls involved, we need to give user some way
//! to find out which call failed with error, so `io::Error` is not an option.
//! We have ``error::Error`` class which describes error as precisely as
//! possible
//!
//! Anyway this is low-level interface. You may want to use some higher level
//! abstraction which mounts filesystems, sets network and monitors processes.
//!
extern crate libc;
extern crate nix;

mod namespace;
mod idmap;
mod chroot;
mod ffi_util;
mod std_api;
mod config;
mod error;
mod pipe;
mod child;
mod run;

pub use error::Error;

use std::ffi::{CString, OsString};
use std::collections::HashMap;
use std::process::Stdio;

use libc::{pid_t};

pub struct Command {
    filename: CString,
    args: Vec<CString>,
    environ: Option<HashMap<OsString, OsString>>,
    config: config::Config,
    stdin: Option<Stdio>,
    stdout: Option<Stdio>,
    stderr: Option<Stdio>,
}

#[derive(Debug)]
pub struct Child {
    pid: pid_t,
    //status: Option<ExitStatus>,
}