NAME
IO::Tty - Low-level allocate a pseudo-Tty
VERSION
0.94_05 BETA
SYNOPSIS
use IO::Tty;
...
# don't use, see IO::Pty for a better way to create ptys.DESCRIPTION
IO::Tty is used internally by IO::Pty to create a pseudo-tty. You wouldn't want to use it directly, use IO::Pty.
Windows is now supported (under the Cygwin environment, see http://source.redhat.com/cygwin).
Please note that pty creation is very system-dependend. From my experience, any modern POSIX system should be fine. Find below a list of systems that IO::Tty should work on.
If you have problems on your system and your system is listed in the "verified" list, you probably have some non-standard setup, e.g. you compiled your Linux-kernel yourself and disabled ptys (bummer!). Please ask your friendly sysadmin for help.
If your system is not listed, unpack the latest version of IO::Tty, do a 'perl Makefile.PL; make; make test; uname -a' and send me (RGiersig@cpan.org) the results and I'll see what I can deduce from that.
If it's working on your system, please send me a short note with details (version number, distribution, etc. 'uname -a' is a good start) so I can get an overview. Thanks!
VERIFIED SYSTEMS, KNOWN ISSUES
This is a list of systems that IO::Tty seems to work on ('make test' passes) with comments about "features":
Linux 2.2.x & 2.4.x
Returns EIO instead of EOF when the slave is closed. Benign.
AIX 4.3
Returns EIO instead of EOF when the slave is closed. Benign.
FreeBSD 4.4
Solaris 8
Has the "feature" of returning EOF just once?!
The following systems have not been verified yet for this version, but a previous version worked on them:
OpenBSD 2.8
The ioctl TIOCSCTTY sometimes fails. This is also known in Tcl/Expect, see http://expect.nist.gov/FAQ.html
SCO Unix v??
HPUX 10.20 & 11.00
There seems to be no way to send an EOF from the slave to the master, so a parent process might not notice that the child went away.
OSF 4.0
Solaris 2.6
Windows NT/2k (under Cygwin)
When you send (print) a too long line (>255 chars ?) to a pty, the call may just hang forever and even alarm() cannot get you out. Don't complain to me...
If you have additions to these lists, please mail them to <RGiersig@cpan.org>.
SEE ALSO
MAILING LISTS
As this module is mainly used by Expect, support for it is available via the two Expect mailing lists, expectperl-announce and expectperl-discuss, at
http://lists.sourceforge.net/lists/listinfo/expectperl-announceand
http://lists.sourceforge.net/lists/listinfo/expectperl-discussAUTHORS
Originally by Graham Barr <gbarr@pobox.com>, based on the Ptty module by Nick Ing-Simmons <nik@tiuk.ti.com>.
Now maintained and heavily rewritten by Roland Giersig <RGiersig@cpan.org>.
Contains copyrighted stuff from openssh v3.0p1, authored by Tatu Ylonen <ylo@cs.hut.fi>, Markus Friedl and Todd C. Miller <Todd.Miller@courtesan.com>. I also got a lot of inspiry from the pty code in Xemacs.
COPYRIGHT
Now all code is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
Nevertheless the above AUTHORS retain their copyrights to the various parts and want to receive credit if their source code is used. See the source for details.
DISCLAIMER
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.