empty - run applications under pseudo-terminal (PTY) sessions to dialogue with interactive programs. Replace TCL/Expect with a simple tool and use your favorite shell (sh, bash, csh, tcsh, ksh, zsh, etc)

Project Activity

See All Activity >

License

BSD License

Follow empty

empty Web Site

You Might Also Like
Automated quote and proposal software for IT solution providers. | ConnectWise CPQ Icon
Automated quote and proposal software for IT solution providers. | ConnectWise CPQ

Create IT quote templates, automate workflows, add integrations & price catalogs to save time & reduce errors on manual data entry & updates.

ConnectWise CPQ, formerly ConnectWise Sell, is a professional quote and proposal automation software for IT solution providers. ConnectWise CPQ offers a wide range of tools that enables IT solution providers to save time, quote more, and win big. Top features include professional quote or proposal templates, product catalog and sourcing, workflow automation, sales reporting, and integrations with best-in-breed solutions like Cisco, Dell, HP, and Salesforce.
Rate This Project
Login To Rate This Project

User Ratings

★★★★★
★★★★
★★★
★★
2
1
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5

User Reviews

  • Using empty to run ssh it echoes strings sent to remote back, example with empty -s ... this happens only when connecting as root user. and after successfully logged in. I did a brief ps for ssh processes and noticed that when connecting as root sshd dosen't open a [priv] instace of sshd for root user instead if runs directly under the main one and opens another one that has pty attached? it's output sent to remote host bounced back as input from remote host in addition to any output from remote host, instead of the normal behavior would be just output from remote host and only when connecting as root empty forks and runs ssh under a pty then uses two fifos to communicate with ssh process the in fifo sees anything I send out the out fifo in addition to the output from the commands i sent via the out fifo I think it's something to do of how sshd behaves when a root user connects something with the sockets or ptys don't know in addition of how empty captures the remote output :/
  • Thanks for good program!
    1 user found this review helpful.
  • This is just what many people need for their developments on a variety of blog about psedo terminal. I still don't know if this will help me with my problem however I found the man page clear and the examples even better to help me on my way. "Empty" is a little poor with error messages. If an "empty" command fails for some reason it just stops with no informative message of why the command failed.
    1 user found this review helpful.
Read more reviews >

Additional Project Details

Operating Systems

Cygwin, Solaris, Linux, OpenBSD, FreeBSD, NetBSD, HP-UX, OpenServer, BSD

Languages

English

User Interface

Console/Terminal, Command-line

Programming Language

Unix Shell, C

Related Categories

Unix Shell Terminals, Unix Shell Software Development Software, Unix Shell System Software, Unix Shell Topic Software, C Terminals, C Software Development Software, C System Software, C Topic Software

Registered

2005-04-18