10 releases

Uses old Rust 2015

0.2.2 Jun 25, 2017
0.2.1 Nov 9, 2016
0.2.0 Sep 5, 2016
0.1.6 Nov 14, 2015
0.1.3 Jul 19, 2015

#9 in #pseudo-terminal

Download history 113/week @ 2024-05-20 97/week @ 2024-05-27 110/week @ 2024-06-03 96/week @ 2024-06-10 138/week @ 2024-06-17 132/week @ 2024-06-24 186/week @ 2024-07-01 64/week @ 2024-07-08 138/week @ 2024-07-15 123/week @ 2024-07-22 127/week @ 2024-07-29 171/week @ 2024-08-05 123/week @ 2024-08-12 173/week @ 2024-08-19 144/week @ 2024-08-26 109/week @ 2024-09-02

563 downloads per month
Used in 10 crates (9 directly)

MIT license

21KB
400 lines

PTY

Crate docs-badge license-badge travis-badge

The pty crate provides pty::fork(). That makes a parent process fork with new pseudo-terminal (PTY).

This crate depends on followings:

  • libc library
  • POSIX environment

Usage

Add this to your Cargo.toml:

[dependencies]
pty = "0.2"

and this to your crate root:

extern crate pty;

pty::fork()

This function returns pty::Child. It represents the child process and its PTY.

For example, the following code spawns tty(1) command by pty::fork() and outputs the result of the command.

extern crate pty;
extern crate libc;

use std::ffi::CString;
use std::io::Read;
use std::ptr;

use pty::fork::*;

fn main() {
  let fork = Fork::from_ptmx().unwrap();

  if let Some(mut master) = fork.is_parent().ok() {
    // Read output via PTY master
    let mut output = String::new();

    match master.read_to_string(&mut output) {
      Ok(_nread) => println!("child tty is: {}", output.trim()),
      Err(e)     => panic!("read error: {}", e),
    }
  }
  else {
    // Child process just exec `tty`
    Command::new("tty").status().expect("could not execute tty");
  }
}

When run this, we get new PTY in the child process.

$ tty
/dev/pts/5
$ cargo run
    Running `target/debug/example`
child tty is: /dev/pts/8

Documentation

API documentation for latest version: http://hibariya.github.io/pty-rs/pty/index.html

Contributing

  1. Fork it ( https://github.com/hibariya/pty-rs/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

License

Copyright (c) 2015 Hika Hibariya

Distributed under the MIT License.

Dependencies

~110KB