Imported upstream version 1.5

[manpages-zh.git] / raw / man1 / perlfaq8.1

.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sh \" Subsection heading
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  | will give a
.\" real vertical bar.  \*(C+ will give a nicer C++.  Capital omega is used to
.\" do unbreakable dashes and therefore won't be available.  \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.tr \(*W-|\(bv\*(Tr
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
'br\}
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.if \nF \{\
.    de IX
.    tm Index:\\$1\t\\n%\t"\\$2"
..
.    nr % 0
.    rr F
.\}
.\"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.hy 0
.if n .na
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \" fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&
.    ds #] \&
.\}
.    \" simple accents for nroff and troff
.if n \{\
.    ds ' \&
.    ds ` \&
.    ds ^ \&
.    ds , \&
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
.IX Title "PERLFAQ8 1"
.TH PERLFAQ8 1 "2003-11-25" "perl v5.8.3" "Perl Programmers Reference Guide"
.SH "NAME"
perlfaq8 \- System Interaction ($Revision: 1.1 $, $Date: 2004/06/16 12:41:53 $)
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
This section of the Perl \s-1FAQ\s0 covers questions involving operating
system interaction.  Topics include interprocess communication (\s-1IPC\s0),
control over the user-interface (keyboard, screen and pointing
devices), and most anything else not related to data manipulation.
.PP
Read the FAQs and documentation specific to the port of perl to your
operating system (eg, perlvms, perlplan9, ...).  These should
contain more detailed information on the vagaries of your perl.
.Sh "How do I find out which operating system I'm running under?"
.IX Subsection "How do I find out which operating system I'm running under?"
The $^O variable ($OSNAME if you use English) contains an indication of
the name of the operating system (not its release number) that your perl
binary was built for.
.Sh "How come \fIexec()\fP doesn't return?"
.IX Subsection "How come exec() doesn't return?"
Because that's what it does: it replaces your currently running
program with a different one.  If you want to keep going (as is
probably the case if you're asking this question) use \fIsystem()\fR
instead.
.Sh "How do I do fancy stuff with the keyboard/screen/mouse?"
.IX Subsection "How do I do fancy stuff with the keyboard/screen/mouse?"
How you access/control keyboards, screens, and pointing devices
(\*(L"mice\*(R") is system\-dependent.  Try the following modules:
.IP "Keyboard" 4
.IX Item "Keyboard"
.Vb 5
\&    Term::Cap                   Standard perl distribution
\&    Term::ReadKey               CPAN
\&    Term::ReadLine::Gnu         CPAN
\&    Term::ReadLine::Perl        CPAN
\&    Term::Screen                CPAN
.Ve
.IP "Screen" 4
.IX Item "Screen"
.Vb 3
\&    Term::Cap                   Standard perl distribution
\&    Curses                      CPAN
\&    Term::ANSIColor             CPAN
.Ve
.IP "Mouse" 4
.IX Item "Mouse"
.Vb 1
\&    Tk                          CPAN
.Ve
.PP
Some of these specific cases are shown below.
.Sh "How do I print something out in color?"
.IX Subsection "How do I print something out in color?"
In general, you don't, because you don't know whether
the recipient has a color-aware display device.  If you
know that they have an \s-1ANSI\s0 terminal that understands
color, you can use the Term::ANSIColor module from \s-1CPAN:\s0
.PP
.Vb 3
\&    use Term::ANSIColor;
\&    print color("red"), "Stop!\en", color("reset");
\&    print color("green"), "Go!\en", color("reset");
.Ve
.PP
Or like this:
.PP
.Vb 3
\&    use Term::ANSIColor qw(:constants);
\&    print RED, "Stop!\en", RESET;
\&    print GREEN, "Go!\en", RESET;
.Ve
.Sh "How do I read just one key without waiting for a return key?"
.IX Subsection "How do I read just one key without waiting for a return key?"
Controlling input buffering is a remarkably system-dependent matter.
On many systems, you can just use the \fBstty\fR command as shown in
\&\*(L"getc\*(R" in perlfunc, but as you see, that's already getting you into
portability snags.
.PP
.Vb 6
\&    open(TTY, "+</dev/tty") or die "no tty: $!";
\&    system "stty  cbreak </dev/tty >/dev/tty 2>&1";
\&    $key = getc(TTY);           # perhaps this works
\&    # OR ELSE
\&    sysread(TTY, $key, 1);      # probably this does
\&    system "stty -cbreak </dev/tty >/dev/tty 2>&1";
.Ve
.PP
The Term::ReadKey module from \s-1CPAN\s0 offers an easy-to-use interface that
should be more efficient than shelling out to \fBstty\fR for each key.
It even includes limited support for Windows.
.PP
.Vb 4
\&    use Term::ReadKey;
\&    ReadMode('cbreak');
\&    $key = ReadKey(0);
\&    ReadMode('normal');
.Ve
.PP
However, using the code requires that you have a working C compiler
and can use it to build and install a \s-1CPAN\s0 module.  Here's a solution
using the standard \s-1POSIX\s0 module, which is already on your systems
(assuming your system supports \s-1POSIX\s0).
.PP
.Vb 2
\&    use HotKey;
\&    $key = readkey();
.Ve
.PP
And here's the HotKey module, which hides the somewhat mystifying calls
to manipulate the \s-1POSIX\s0 termios structures.
.PP
.Vb 2
\&    # HotKey.pm
\&    package HotKey;
.Ve
.PP
.Vb 2
\&    @ISA = qw(Exporter);
\&    @EXPORT = qw(cbreak cooked readkey);
.Ve
.PP
.Vb 3
\&    use strict;
\&    use POSIX qw(:termios_h);
\&    my ($term, $oterm, $echo, $noecho, $fd_stdin);
.Ve
.PP
.Vb 4
\&    $fd_stdin = fileno(STDIN);
\&    $term     = POSIX::Termios->new();
\&    $term->getattr($fd_stdin);
\&    $oterm     = $term->getlflag();
.Ve
.PP
.Vb 2
\&    $echo     = ECHO | ECHOK | ICANON;
\&    $noecho   = $oterm & ~$echo;
.Ve
.PP
.Vb 5
\&    sub cbreak {
\&        $term->setlflag($noecho);  # ok, so i don't want echo either
\&        $term->setcc(VTIME, 1);
\&        $term->setattr($fd_stdin, TCSANOW);
\&    }
.Ve
.PP
.Vb 5
\&    sub cooked {
\&        $term->setlflag($oterm);
\&        $term->setcc(VTIME, 0);
\&        $term->setattr($fd_stdin, TCSANOW);
\&    }
.Ve
.PP
.Vb 7
\&    sub readkey {
\&        my $key = '';
\&        cbreak();
\&        sysread(STDIN, $key, 1);
\&        cooked();
\&        return $key;
\&    }
.Ve
.PP
.Vb 1
\&    END { cooked() }
.Ve
.PP
.Vb 1
\&    1;
.Ve
.Sh "How do I check whether input is ready on the keyboard?"
.IX Subsection "How do I check whether input is ready on the keyboard?"
The easiest way to do this is to read a key in nonblocking mode with the
Term::ReadKey module from \s-1CPAN\s0, passing it an argument of \-1 to indicate
not to block:
.PP
.Vb 1
\&    use Term::ReadKey;
.Ve
.PP
.Vb 1
\&    ReadMode('cbreak');
.Ve
.PP
.Vb 5
\&    if (defined ($char = ReadKey(-1)) ) {
\&        # input was waiting and it was $char
\&    } else {
\&        # no input was waiting
\&    }
.Ve
.PP
.Vb 1
\&    ReadMode('normal');                  # restore normal tty settings
.Ve
.Sh "How do I clear the screen?"
.IX Subsection "How do I clear the screen?"
If you only have do so infrequently, use \f(CW\*(C`system\*(C'\fR:
.PP
.Vb 1
\&    system("clear");
.Ve
.PP
If you have to do this a lot, save the clear string
so you can print it 100 times without calling a program
100 times:
.PP
.Vb 2
\&    $clear_string = `clear`;
\&    print $clear_string;
.Ve
.PP
If you're planning on doing other screen manipulations, like cursor
positions, etc, you might wish to use Term::Cap module:
.PP
.Vb 3
\&    use Term::Cap;
\&    $terminal = Term::Cap->Tgetent( {OSPEED => 9600} );
\&    $clear_string = $terminal->Tputs('cl');
.Ve
.Sh "How do I get the screen size?"
.IX Subsection "How do I get the screen size?"
If you have Term::ReadKey module installed from \s-1CPAN\s0,
you can use it to fetch the width and height in characters
and in pixels:
.PP
.Vb 2
\&    use Term::ReadKey;
\&    ($wchar, $hchar, $wpixels, $hpixels) = GetTerminalSize();
.Ve
.PP
This is more portable than the raw \f(CW\*(C`ioctl\*(C'\fR, but not as
illustrative:
.PP
.Vb 10
\&    require 'sys/ioctl.ph';
\&    die "no TIOCGWINSZ " unless defined &TIOCGWINSZ;
\&    open(TTY, "+</dev/tty")                     or die "No tty: $!";
\&    unless (ioctl(TTY, &TIOCGWINSZ, $winsize='')) {
\&        die sprintf "$0: ioctl TIOCGWINSZ (%08x: $!)\en", &TIOCGWINSZ;
\&    }
\&    ($row, $col, $xpixel, $ypixel) = unpack('S4', $winsize);
\&    print "(row,col) = ($row,$col)";
\&    print "  (xpixel,ypixel) = ($xpixel,$ypixel)" if $xpixel || $ypixel;
\&    print "\en";
.Ve
.Sh "How do I ask the user for a password?"
.IX Subsection "How do I ask the user for a password?"
(This question has nothing to do with the web.  See a different
\&\s-1FAQ\s0 for that.)
.PP
There's an example of this in \*(L"crypt\*(R" in perlfunc).  First, you put the
terminal into \*(L"no echo\*(R" mode, then just read the password normally.
You may do this with an old-style \fIioctl()\fR function, \s-1POSIX\s0 terminal
control (see \s-1POSIX\s0 or its documentation the Camel Book), or a call
to the \fBstty\fR program, with varying degrees of portability.
.PP
You can also do this for most systems using the Term::ReadKey module
from \s-1CPAN\s0, which is easier to use and in theory more portable.
.PP
.Vb 1
\&    use Term::ReadKey;
.Ve
.PP
.Vb 2
\&    ReadMode('noecho');
\&    $password = ReadLine(0);
.Ve
.Sh "How do I read and write the serial port?"
.IX Subsection "How do I read and write the serial port?"
This depends on which operating system your program is running on.  In
the case of Unix, the serial ports will be accessible through files in
/dev; on other systems, device names will doubtless differ.
Several problem areas common to all device interaction are the
following:
.IP "lockfiles" 4
.IX Item "lockfiles"
Your system may use lockfiles to control multiple access.  Make sure
you follow the correct protocol.  Unpredictable behavior can result
from multiple processes reading from one device.
.IP "open mode" 4
.IX Item "open mode"
If you expect to use both read and write operations on the device,
you'll have to open it for update (see \*(L"open\*(R" in perlfunc for
details).  You may wish to open it without running the risk of
blocking by using \fIsysopen()\fR and \f(CW\*(C`O_RDWR|O_NDELAY|O_NOCTTY\*(C'\fR from the
Fcntl module (part of the standard perl distribution).  See
\&\*(L"sysopen\*(R" in perlfunc for more on this approach.
.IP "end of line" 4
.IX Item "end of line"
Some devices will be expecting a \*(L"\er\*(R" at the end of each line rather
than a \*(L"\en\*(R".  In some ports of perl, \*(L"\er\*(R" and \*(L"\en\*(R" are different from
their usual (Unix) \s-1ASCII\s0 values of \*(L"\e012\*(R" and \*(L"\e015\*(R".  You may have to
give the numeric values you want directly, using octal (\*(L"\e015\*(R"), hex
(\*(L"0x0D\*(R"), or as a control-character specification (\*(L"\ecM\*(R").
.Sp
.Vb 2
\&    print DEV "atv1\e012";       # wrong, for some devices
\&    print DEV "atv1\e015";       # right, for some devices
.Ve
.Sp
Even though with normal text files a \*(L"\en\*(R" will do the trick, there is
still no unified scheme for terminating a line that is portable
between Unix, DOS/Win, and Macintosh, except to terminate \fI\s-1ALL\s0\fR line
ends with \*(L"\e015\e012\*(R", and strip what you don't need from the output.
This applies especially to socket I/O and autoflushing, discussed
next.
.IP "flushing output" 4
.IX Item "flushing output"
If you expect characters to get to your device when you \fIprint()\fR them,
you'll want to autoflush that filehandle.  You can use \fIselect()\fR
and the \f(CW$|\fR variable to control autoflushing (see "$|" in perlvar
and \*(L"select\*(R" in perlfunc, or perlfaq5, ``How do I flush/unbuffer an
output filehandle?  Why must I do this?''):
.Sp
.Vb 3
\&    $oldh = select(DEV);
\&    $| = 1;
\&    select($oldh);
.Ve
.Sp
You'll also see code that does this without a temporary variable, as in
.Sp
.Vb 1
\&    select((select(DEV), $| = 1)[0]);
.Ve
.Sp
Or if you don't mind pulling in a few thousand lines
of code just because you're afraid of a little $| variable:
.Sp
.Vb 2
\&    use IO::Handle;
\&    DEV->autoflush(1);
.Ve
.Sp
As mentioned in the previous item, this still doesn't work when using
socket I/O between Unix and Macintosh.  You'll need to hard code your
line terminators, in that case.
.IP "non-blocking input" 4
.IX Item "non-blocking input"
If you are doing a blocking \fIread()\fR or \fIsysread()\fR, you'll have to
arrange for an alarm handler to provide a timeout (see
\&\*(L"alarm\*(R" in perlfunc).  If you have a non-blocking open, you'll likely
have a non-blocking read, which means you may have to use a 4\-arg
\&\fIselect()\fR to determine whether I/O is ready on that device (see
\&\*(L"select\*(R" in perlfunc.
.PP
While trying to read from his caller-id box, the notorious Jamie Zawinski
<jwz@netscape.com>, after much gnashing of teeth and fighting with sysread,
sysopen, \s-1POSIX\s0's tcgetattr business, and various other functions that
go bump in the night, finally came up with this:
.PP
.Vb 13
\&    sub open_modem {
\&        use IPC::Open2;
\&        my $stty = `/bin/stty -g`;
\&        open2( \e*MODEM_IN, \e*MODEM_OUT, "cu -l$modem_device -s2400 2>&1");
\&        # starting cu hoses /dev/tty's stty settings, even when it has
\&        # been opened on a pipe...
\&        system("/bin/stty $stty");
\&        $_ = <MODEM_IN>;
\&        chomp;
\&        if ( !m/^Connected/ ) {
\&            print STDERR "$0: cu printed `$_' instead of `Connected'\en";
\&        }
\&    }
.Ve
.Sh "How do I decode encrypted password files?"
.IX Subsection "How do I decode encrypted password files?"
You spend lots and lots of money on dedicated hardware, but this is
bound to get you talked about.
.PP
Seriously, you can't if they are Unix password files\*(--the Unix
password system employs one-way encryption.  It's more like hashing than
encryption.  The best you can check is whether something else hashes to
the same string.  You can't turn a hash back into the original string.
Programs like Crack
can forcibly (and intelligently) try to guess passwords, but don't
(can't) guarantee quick success.
.PP
If you're worried about users selecting bad passwords, you should
proactively check when they try to change their password (by modifying
\&\fIpasswd\fR\|(1), for example).
.Sh "How do I start a process in the background?"
.IX Subsection "How do I start a process in the background?"
Several modules can start other processes that do not block
your Perl program.  You can use IPC::Open3, Parallel::Jobs,
IPC::Run, and some of the \s-1POE\s0 modules.  See \s-1CPAN\s0 for more
details.
.PP
You could also use
.PP
.Vb 1
\&    system("cmd &")
.Ve
.PP
or you could use fork as documented in \*(L"fork\*(R" in perlfunc, with
further examples in perlipc.  Some things to be aware of, if you're
on a Unix-like system:
.IP "\s-1STDIN\s0, \s-1STDOUT\s0, and \s-1STDERR\s0 are shared" 4
.IX Item "STDIN, STDOUT, and STDERR are shared"
Both the main process and the backgrounded one (the \*(L"child\*(R" process)
share the same \s-1STDIN\s0, \s-1STDOUT\s0 and \s-1STDERR\s0 filehandles.  If both try to
access them at once, strange things can happen.  You may want to close
or reopen these for the child.  You can get around this with
\&\f(CW\*(C`open\*(C'\fRing a pipe (see \*(L"open\*(R" in perlfunc) but on some systems this
means that the child process cannot outlive the parent.
.IP "Signals" 4
.IX Item "Signals"
You'll have to catch the \s-1SIGCHLD\s0 signal, and possibly \s-1SIGPIPE\s0 too.
\&\s-1SIGCHLD\s0 is sent when the backgrounded process finishes.  \s-1SIGPIPE\s0 is
sent when you write to a filehandle whose child process has closed (an
untrapped \s-1SIGPIPE\s0 can cause your program to silently die).  This is
not an issue with \f(CW\*(C`system("cmd&")\*(C'\fR.
.IP "Zombies" 4
.IX Item "Zombies"
You have to be prepared to \*(L"reap\*(R" the child process when it finishes.
.Sp
.Vb 1
\&    $SIG{CHLD} = sub { wait };
.Ve
.Sp
.Vb 1
\&    $SIG{CHLD} = 'IGNORE';
.Ve
.Sp
You can also use a double fork. You immediately \fIwait()\fR for your
first child, and the init daemon will \fIwait()\fR for your grandchild once
it exits.
.Sp
.Vb 8
\&        unless ($pid = fork) {
\&                unless (fork) {
\&            exec "what you really wanna do";
\&            die "exec failed!";
\&                }
\&        exit 0;
\&        }
\&    waitpid($pid,0);
.Ve
.Sp
See \*(L"Signals\*(R" in perlipc for other examples of code to do this.
Zombies are not an issue with \f(CW\*(C`system("prog &")\*(C'\fR.
.Sh "How do I trap control characters/signals?"
.IX Subsection "How do I trap control characters/signals?"
You don't actually \*(L"trap\*(R" a control character.  Instead, that character
generates a signal which is sent to your terminal's currently
foregrounded process group, which you then trap in your process.
Signals are documented in \*(L"Signals\*(R" in perlipc and the
section on ``Signals'' in the Camel.
.PP
Be warned that very few C libraries are re\-entrant.  Therefore, if you
attempt to \fIprint()\fR in a handler that got invoked during another stdio
operation your internal structures will likely be in an
inconsistent state, and your program will dump core.  You can
sometimes avoid this by using \fIsyswrite()\fR instead of \fIprint()\fR.
.PP
Unless you're exceedingly careful, the only safe things to do inside a
signal handler are (1) set a variable and (2) exit.  In the first case,
you should only set a variable in such a way that \fImalloc()\fR is not
called (eg, by setting a variable that already has a value).
.PP
For example:
.PP
.Vb 5
\&    $Interrupted = 0;   # to ensure it has a value
\&    $SIG{INT} = sub {
\&        $Interrupted++;
\&        syswrite(STDERR, "ouch\en", 5);
\&    }
.Ve
.PP
However, because syscalls restart by default, you'll find that if
you're in a \*(L"slow\*(R" call, such as <\s-1FH\s0>, \fIread()\fR, \fIconnect()\fR, or
\&\fIwait()\fR, that the only way to terminate them is by \*(L"longjumping\*(R" out;
that is, by raising an exception.  See the time-out handler for a
blocking \fIflock()\fR in \*(L"Signals\*(R" in perlipc or the section on ``Signals''
in the Camel book.
.Sh "How do I modify the shadow password file on a Unix system?"
.IX Subsection "How do I modify the shadow password file on a Unix system?"
If perl was installed correctly and your shadow library was written
properly, the getpw*() functions described in perlfunc should in
theory provide (read\-only) access to entries in the shadow password
file.  To change the file, make a new shadow password file (the format
varies from system to system\*(--see passwd for specifics) and use
\&\fIpwd_mkdb\fR\|(8) to install it (see pwd_mkdb for more details).
.Sh "How do I set the time and date?"
.IX Subsection "How do I set the time and date?"
Assuming you're running under sufficient permissions, you should be
able to set the system-wide date and time by running the \fIdate\fR\|(1)
program.  (There is no way to set the time and date on a per-process
basis.)  This mechanism will work for Unix, \s-1MS\-DOS\s0, Windows, and \s-1NT\s0;
the \s-1VMS\s0 equivalent is \f(CW\*(C`set time\*(C'\fR.
.PP
However, if all you want to do is change your time zone, you can
probably get away with setting an environment variable:
.PP
.Vb 3
\&    $ENV{TZ} = "MST7MDT";                  # unixish
\&    $ENV{'SYS$TIMEZONE_DIFFERENTIAL'}="-5" # vms
\&    system "trn comp.lang.perl.misc";
.Ve
.Sh "How can I \fIsleep()\fP or \fIalarm()\fP for under a second?"
.IX Subsection "How can I sleep() or alarm() for under a second?"
If you want finer granularity than the 1 second that the \fIsleep()\fR
function provides, the easiest way is to use the \fIselect()\fR function as
documented in \*(L"select\*(R" in perlfunc.  Try the Time::HiRes and
the BSD::Itimer modules (available from \s-1CPAN\s0, and starting from
Perl 5.8 Time::HiRes is part of the standard distribution).
.Sh "How can I measure time under a second?"
.IX Subsection "How can I measure time under a second?"
In general, you may not be able to.  The Time::HiRes module (available
from \s-1CPAN\s0, and starting from Perl 5.8 part of the standard distribution)
provides this functionality for some systems.
.PP
If your system supports both the \fIsyscall()\fR function in Perl as well as
a system call like \fIgettimeofday\fR\|(2), then you may be able to do
something like this:
.PP
.Vb 1
\&    require 'sys/syscall.ph';
.Ve
.PP
.Vb 1
\&    $TIMEVAL_T = "LL";
.Ve
.PP
.Vb 1
\&    $done = $start = pack($TIMEVAL_T, ());
.Ve
.PP
.Vb 2
\&    syscall(&SYS_gettimeofday, $start, 0) != -1
\&               or die "gettimeofday: $!";
.Ve
.PP
.Vb 3
\&       ##########################
\&       # DO YOUR OPERATION HERE #
\&       ##########################
.Ve
.PP
.Vb 2
\&    syscall( &SYS_gettimeofday, $done, 0) != -1
\&           or die "gettimeofday: $!";
.Ve
.PP
.Vb 2
\&    @start = unpack($TIMEVAL_T, $start);
\&    @done  = unpack($TIMEVAL_T, $done);
.Ve
.PP
.Vb 2
\&    # fix microseconds
\&    for ($done[1], $start[1]) { $_ /= 1_000_000 }
.Ve
.PP
.Vb 3
\&    $delta_time = sprintf "%.4f", ($done[0]  + $done[1]  )
\&                                            -
\&                                 ($start[0] + $start[1] );
.Ve
.Sh "How can I do an \fIatexit()\fP or \fIsetjmp()\fP/\fIlongjmp()\fP? (Exception handling)"
.IX Subsection "How can I do an atexit() or setjmp()/longjmp()? (Exception handling)"
Release 5 of Perl added the \s-1END\s0 block, which can be used to simulate
\&\fIatexit()\fR.  Each package's \s-1END\s0 block is called when the program or
thread ends (see perlmod manpage for more details).
.PP
For example, you can use this to make sure your filter program
managed to finish its output without filling up the disk:
.PP
.Vb 3
\&    END {
\&        close(STDOUT) || die "stdout close failed: $!";
\&    }
.Ve
.PP
The \s-1END\s0 block isn't called when untrapped signals kill the program,
though, so if you use \s-1END\s0 blocks you should also use
.PP
.Vb 1
\&        use sigtrap qw(die normal-signals);
.Ve
.PP
Perl's exception-handling mechanism is its \fIeval()\fR operator.  You can
use \fIeval()\fR as setjmp and \fIdie()\fR as longjmp.  For details of this, see
the section on signals, especially the time-out handler for a blocking
\&\fIflock()\fR in \*(L"Signals\*(R" in perlipc or the section on ``Signals'' in
the Camel Book.
.PP
If exception handling is all you're interested in, try the
exceptions.pl library (part of the standard perl distribution).
.PP
If you want the \fIatexit()\fR syntax (and an \fIrmexit()\fR as well), try the
AtExit module available from \s-1CPAN\s0.
.ie n .Sh "Why doesn't my sockets program work under System V (Solaris)?  What does the error message ""Protocol not supported"" mean?"
.el .Sh "Why doesn't my sockets program work under System V (Solaris)?  What does the error message ``Protocol not supported'' mean?"
.IX Subsection "Why doesn't my sockets program work under System V (Solaris)?  What does the error message Protocol not supported mean?"
Some Sys-V based systems, notably Solaris 2.X, redefined some of the
standard socket constants.  Since these were constant across all
architectures, they were often hardwired into perl code.  The proper
way to deal with this is to \*(L"use Socket\*(R" to get the correct values.
.PP
Note that even though SunOS and Solaris are binary compatible, these
values are different.  Go figure.
.Sh "How can I call my system's unique C functions from Perl?"
.IX Subsection "How can I call my system's unique C functions from Perl?"
In most cases, you write an external module to do it\*(--see the answer
to \*(L"Where can I learn about linking C with Perl? [h2xs, xsubpp]\*(R".
However, if the function is a system call, and your system supports
\&\fIsyscall()\fR, you can use the syscall function (documented in
perlfunc).
.PP
Remember to check the modules that came with your distribution, and
\&\s-1CPAN\s0 as well\-\-\-someone may already have written a module to do it. On
Windows, try Win32::API.  On Macs, try Mac::Carbon.  If no module
has an interface to the C function, you can inline a bit of C in your
Perl source with Inline::C.
.Sh "Where do I get the include files to do \fIioctl()\fP or \fIsyscall()\fP?"
.IX Subsection "Where do I get the include files to do ioctl() or syscall()?"
Historically, these would be generated by the h2ph tool, part of the
standard perl distribution.  This program converts \fIcpp\fR\|(1) directives
in C header files to files containing subroutine definitions, like
&SYS_getitimer, which you can use as arguments to your functions.
It doesn't work perfectly, but it usually gets most of the job done.
Simple files like \fIerrno.h\fR, \fIsyscall.h\fR, and \fIsocket.h\fR were fine,
but the hard ones like \fIioctl.h\fR nearly always need to hand\-edited.
Here's how to install the *.ph files:
.PP
.Vb 3
\&    1.  become super-user
\&    2.  cd /usr/include
\&    3.  h2ph *.h */*.h
.Ve
.PP
If your system supports dynamic loading, for reasons of portability and
sanity you probably ought to use h2xs (also part of the standard perl
distribution).  This tool converts C header files to Perl extensions.
See perlxstut for how to get started with h2xs.
.PP
If your system doesn't support dynamic loading, you still probably
ought to use h2xs.  See perlxstut and ExtUtils::MakeMaker for
more information (in brief, just use \fBmake perl\fR instead of a plain
\&\fBmake\fR to rebuild perl with a new static extension).
.Sh "Why do setuid perl scripts complain about kernel problems?"
.IX Subsection "Why do setuid perl scripts complain about kernel problems?"
Some operating systems have bugs in the kernel that make setuid
scripts inherently insecure.  Perl gives you a number of options
(described in perlsec) to work around such systems.
.Sh "How can I open a pipe both to and from a command?"
.IX Subsection "How can I open a pipe both to and from a command?"
The IPC::Open2 module (part of the standard perl distribution) is an
easy-to-use approach that internally uses \fIpipe()\fR, \fIfork()\fR, and \fIexec()\fR to do
the job.  Make sure you read the deadlock warnings in its documentation,
though (see IPC::Open2).  See
\&\*(L"Bidirectional Communication with Another Process\*(R" in perlipc and
\&\*(L"Bidirectional Communication with Yourself\*(R" in perlipc
.PP
You may also use the IPC::Open3 module (part of the standard perl
distribution), but be warned that it has a different order of
arguments from IPC::Open2 (see IPC::Open3).
.Sh "Why can't I get the output of a command with \fIsystem()\fP?"
.IX Subsection "Why can't I get the output of a command with system()?"
You're confusing the purpose of \fIsystem()\fR and backticks (``).  \fIsystem()\fR
runs a command and returns exit status information (as a 16 bit value:
the low 7 bits are the signal the process died from, if any, and
the high 8 bits are the actual exit value).  Backticks (``) run a
command and return what it sent to \s-1STDOUT\s0.
.PP
.Vb 2
\&    $exit_status   = system("mail-users");
\&    $output_string = `ls`;
.Ve
.Sh "How can I capture \s-1STDERR\s0 from an external command?"
.IX Subsection "How can I capture STDERR from an external command?"
There are three basic ways of running external commands:
.PP
.Vb 3
\&    system $cmd;                # using system()
\&    $output = `$cmd`;           # using backticks (``)
\&    open (PIPE, "cmd |");       # using open()
.Ve
.PP
With \fIsystem()\fR, both \s-1STDOUT\s0 and \s-1STDERR\s0 will go the same place as the
script's \s-1STDOUT\s0 and \s-1STDERR\s0, unless the \fIsystem()\fR command redirects them.
Backticks and \fIopen()\fR read \fBonly\fR the \s-1STDOUT\s0 of your command.
.PP
You can also use the \fIopen3()\fR function from IPC::Open3.  Benjamin
Goldberg provides some sample code:
.PP
To capture a program's \s-1STDOUT\s0, but discard its \s-1STDERR:\s0
.PP
.Vb 7
\&    use IPC::Open3;
\&    use File::Spec;
\&    use Symbol qw(gensym);
\&    open(NULL, ">", File::Spec->devnull);
\&    my $pid = open3(gensym, \e*PH, ">&NULL", "cmd");
\&    while( <PH> ) { }
\&    waitpid($pid, 0);
.Ve
.PP
To capture a program's \s-1STDERR\s0, but discard its \s-1STDOUT:\s0
.PP
.Vb 7
\&    use IPC::Open3;
\&    use File::Spec;
\&    use Symbol qw(gensym);
\&    open(NULL, ">", File::Spec->devnull);
\&    my $pid = open3(gensym, ">&NULL", \e*PH, "cmd");
\&    while( <PH> ) { }
\&    waitpid($pid, 0);
.Ve
.PP
To capture a program's \s-1STDERR\s0, and let its \s-1STDOUT\s0 go to our own \s-1STDERR:\s0
.PP
.Vb 5
\&    use IPC::Open3;
\&    use Symbol qw(gensym);
\&    my $pid = open3(gensym, ">&STDERR", \e*PH, "cmd");
\&    while( <PH> ) { }
\&    waitpid($pid, 0);
.Ve
.PP
To read both a command's \s-1STDOUT\s0 and its \s-1STDERR\s0 separately, you can
redirect them to temp files, let the command run, then read the temp
files:
.PP
.Vb 10
\&    use IPC::Open3;
\&    use Symbol qw(gensym);
\&    use IO::File;
\&    local *CATCHOUT = IO::File->new_tempfile;
\&    local *CATCHERR = IO::File->new_tempfile;
\&    my $pid = open3(gensym, ">&CATCHOUT", ">&CATCHERR", "cmd");
\&    waitpid($pid, 0);
\&    seek $_, 0, 0 for \e*CATCHOUT, \e*CATCHERR;
\&    while( <CATCHOUT> ) {}
\&    while( <CATCHERR> ) {}
.Ve
.PP
But there's no real need for *both* to be tempfiles... the following
should work just as well, without deadlocking:
.PP
.Vb 9
\&    use IPC::Open3;
\&    use Symbol qw(gensym);
\&    use IO::File;
\&    local *CATCHERR = IO::File->new_tempfile;
\&    my $pid = open3(gensym, \e*CATCHOUT, ">&CATCHERR", "cmd");
\&    while( <CATCHOUT> ) {}
\&    waitpid($pid, 0);
\&    seek CATCHERR, 0, 0;
\&    while( <CATCHERR> ) {}
.Ve
.PP
And it'll be faster, too, since we can begin processing the program's
stdout immediately, rather than waiting for the program to finish.
.PP
With any of these, you can change file descriptors before the call:
.PP
.Vb 2
\&    open(STDOUT, ">logfile");
\&    system("ls");
.Ve
.PP
or you can use Bourne shell file-descriptor redirection:
.PP
.Vb 2
\&    $output = `$cmd 2>some_file`;
\&    open (PIPE, "cmd 2>some_file |");
.Ve
.PP
You can also use file-descriptor redirection to make \s-1STDERR\s0 a
duplicate of \s-1STDOUT:\s0
.PP
.Vb 2
\&    $output = `$cmd 2>&1`;
\&    open (PIPE, "cmd 2>&1 |");
.Ve
.PP
Note that you \fIcannot\fR simply open \s-1STDERR\s0 to be a dup of \s-1STDOUT\s0
in your Perl program and avoid calling the shell to do the redirection.
This doesn't work:
.PP
.Vb 2
\&    open(STDERR, ">&STDOUT");
\&    $alloutput = `cmd args`;  # stderr still escapes
.Ve
.PP
This fails because the \fIopen()\fR makes \s-1STDERR\s0 go to where \s-1STDOUT\s0 was
going at the time of the \fIopen()\fR.  The backticks then make \s-1STDOUT\s0 go to
a string, but don't change \s-1STDERR\s0 (which still goes to the old
\&\s-1STDOUT\s0).
.PP
Note that you \fImust\fR use Bourne shell (\fIsh\fR\|(1)) redirection syntax in
backticks, not \fIcsh\fR\|(1)!  Details on why Perl's \fIsystem()\fR and backtick
and pipe opens all use the Bourne shell are in the
\&\fIversus/csh.whynot\fR article in the \*(L"Far More Than You Ever Wanted To
Know\*(R" collection in http://www.cpan.org/misc/olddoc/FMTEYEWTK.tgz .  To
capture a command's \s-1STDERR\s0 and \s-1STDOUT\s0 together:
.PP
.Vb 3
\&    $output = `cmd 2>&1`;                       # either with backticks
\&    $pid = open(PH, "cmd 2>&1 |");              # or with an open pipe
\&    while (<PH>) { }                            #    plus a read
.Ve
.PP
To capture a command's \s-1STDOUT\s0 but discard its \s-1STDERR:\s0
.PP
.Vb 3
\&    $output = `cmd 2>/dev/null`;                # either with backticks
\&    $pid = open(PH, "cmd 2>/dev/null |");       # or with an open pipe
\&    while (<PH>) { }                            #    plus a read
.Ve
.PP
To capture a command's \s-1STDERR\s0 but discard its \s-1STDOUT:\s0
.PP
.Vb 3
\&    $output = `cmd 2>&1 1>/dev/null`;           # either with backticks
\&    $pid = open(PH, "cmd 2>&1 1>/dev/null |");  # or with an open pipe
\&    while (<PH>) { }                            #    plus a read
.Ve
.PP
To exchange a command's \s-1STDOUT\s0 and \s-1STDERR\s0 in order to capture the \s-1STDERR\s0
but leave its \s-1STDOUT\s0 to come out our old \s-1STDERR:\s0
.PP
.Vb 3
\&    $output = `cmd 3>&1 1>&2 2>&3 3>&-`;        # either with backticks
\&    $pid = open(PH, "cmd 3>&1 1>&2 2>&3 3>&-|");# or with an open pipe
\&    while (<PH>) { }                            #    plus a read
.Ve
.PP
To read both a command's \s-1STDOUT\s0 and its \s-1STDERR\s0 separately, it's easiest
and safest to redirect them separately to files, and then read from those
files when the program is done:
.PP
.Vb 1
\&    system("program args 1>/tmp/program.stdout 2>/tmp/program.stderr");
.Ve
.PP
Ordering is important in all these examples.  That's because the shell
processes file descriptor redirections in strictly left to right order.
.PP
.Vb 2
\&    system("prog args 1>tmpfile 2>&1");
\&    system("prog args 2>&1 1>tmpfile");
.Ve
.PP
The first command sends both standard out and standard error to the
temporary file.  The second command sends only the old standard output
there, and the old standard error shows up on the old standard out.
.Sh "Why doesn't \fIopen()\fP return an error when a pipe open fails?"
.IX Subsection "Why doesn't open() return an error when a pipe open fails?"
If the second argument to a piped \fIopen()\fR contains shell
metacharacters, perl \fIfork()\fRs, then \fIexec()\fRs a shell to decode the
metacharacters and eventually run the desired program.  If the program
couldn't be run, it's the shell that gets the message, not Perl. All
your Perl program can find out is whether the shell itself could be
successfully started.  You can still capture the shell's \s-1STDERR\s0 and
check it for error messages.  See \*(L"How can I capture \s-1STDERR\s0 from an external command?\*(R" elsewhere in this document, or use the
IPC::Open3 module.
.PP
If there are no shell metacharacters in the argument of \fIopen()\fR, Perl
runs the command directly, without using the shell, and can correctly
report whether the command started.
.Sh "What's wrong with using backticks in a void context?"
.IX Subsection "What's wrong with using backticks in a void context?"
Strictly speaking, nothing.  Stylistically speaking, it's not a good
way to write maintainable code.  Perl has several operators for
running external commands.  Backticks are one; they collect the output
from the command for use in your program.  The \f(CW\*(C`system\*(C'\fR function is
another; it doesn't do this.
.PP
Writing backticks in your program sends a clear message to the readers
of your code that you wanted to collect the output of the command.
Why send a clear message that isn't true?
.PP
Consider this line:
.PP
.Vb 1
\&    `cat /etc/termcap`;
.Ve
.PP
You forgot to check \f(CW$?\fR to see whether the program even ran
correctly.  Even if you wrote
.PP
.Vb 1
\&    print `cat /etc/termcap`;
.Ve
.PP
this code could and probably should be written as
.PP
.Vb 2
\&    system("cat /etc/termcap") == 0
\&        or die "cat program failed!";
.Ve
.PP
which will get the output quickly (as it is generated, instead of only
at the end) and also check the return value.
.PP
\&\fIsystem()\fR also provides direct control over whether shell wildcard
processing may take place, whereas backticks do not.
.Sh "How can I call backticks without shell processing?"
.IX Subsection "How can I call backticks without shell processing?"
This is a bit tricky.  You can't simply write the command
like this:
.PP
.Vb 1
\&    @ok = `grep @opts '$search_string' @filenames`;
.Ve
.PP
As of Perl 5.8.0, you can use \fIopen()\fR with multiple arguments.
Just like the list forms of \fIsystem()\fR and \fIexec()\fR, no shell
escapes happen.
.PP
.Vb 3
\&   open( GREP, "-|", 'grep', @opts, $search_string, @filenames );
\&   chomp(@ok = <GREP>);
\&   close GREP;
.Ve
.PP
You can also:
.PP
.Vb 10
\&    my @ok = ();
\&    if (open(GREP, "-|")) {
\&        while (<GREP>) {
\&            chomp;
\&            push(@ok, $_);
\&        }
\&        close GREP;
\&    } else {
\&        exec 'grep', @opts, $search_string, @filenames;
\&    }
.Ve
.PP
Just as with \fIsystem()\fR, no shell escapes happen when you \fIexec()\fR a list.
Further examples of this can be found in \*(L"Safe Pipe Opens\*(R" in perlipc.
.PP
Note that if you're use Microsoft, no solution to this vexing issue
is even possible.  Even if Perl were to emulate \fIfork()\fR, you'd still
be stuck, because Microsoft does not have a argc/argv\-style \s-1API\s0.
.Sh "Why can't my script read from \s-1STDIN\s0 after I gave it \s-1EOF\s0 (^D on Unix, ^Z on \s-1MS\-DOS\s0)?"
.IX Subsection "Why can't my script read from STDIN after I gave it EOF (^D on Unix, ^Z on MS-DOS)?"
Some stdio's set error and eof flags that need clearing.  The
\&\s-1POSIX\s0 module defines \fIclearerr()\fR that you can use.  That is the
technically correct way to do it.  Here are some less reliable
workarounds:
.IP "1" 4
.IX Item "1"
Try keeping around the seekpointer and go there, like this:
.Sp
.Vb 2
\&    $where = tell(LOG);
\&    seek(LOG, $where, 0);
.Ve
.IP "2" 4
.IX Item "2"
If that doesn't work, try seeking to a different part of the file and
then back.
.IP "3" 4
.IX Item "3"
If that doesn't work, try seeking to a different part of
the file, reading something, and then seeking back.
.IP "4" 4
.IX Item "4"
If that doesn't work, give up on your stdio package and use sysread.
.Sh "How can I convert my shell script to perl?"
.IX Subsection "How can I convert my shell script to perl?"
Learn Perl and rewrite it.  Seriously, there's no simple converter.
Things that are awkward to do in the shell are easy to do in Perl, and
this very awkwardness is what would make a shell\->perl converter
nigh-on impossible to write.  By rewriting it, you'll think about what
you're really trying to do, and hopefully will escape the shell's
pipeline datastream paradigm, which while convenient for some matters,
causes many inefficiencies.
.Sh "Can I use perl to run a telnet or ftp session?"
.IX Subsection "Can I use perl to run a telnet or ftp session?"
Try the Net::FTP, TCP::Client, and Net::Telnet modules (available from
\&\s-1CPAN\s0).  http://www.cpan.org/scripts/netstuff/telnet.emul.shar
will also help for emulating the telnet protocol, but Net::Telnet is
quite probably easier to use..
.PP
If all you want to do is pretend to be telnet but don't need
the initial telnet handshaking, then the standard dual-process
approach will suffice:
.PP
.Vb 12
\&    use IO::Socket;             # new in 5.004
\&    $handle = IO::Socket::INET->new('www.perl.com:80')
\&            || die "can't connect to port 80 on www.perl.com: $!";
\&    $handle->autoflush(1);
\&    if (fork()) {               # XXX: undef means failure
\&        select($handle);
\&        print while <STDIN>;    # everything from stdin to socket
\&    } else {
\&        print while <$handle>;  # everything from socket to stdout
\&    }
\&    close $handle;
\&    exit;
.Ve
.Sh "How can I write expect in Perl?"
.IX Subsection "How can I write expect in Perl?"
Once upon a time, there was a library called chat2.pl (part of the
standard perl distribution), which never really got finished.  If you
find it somewhere, \fIdon't use it\fR.  These days, your best bet is to
look at the Expect module available from \s-1CPAN\s0, which also requires two
other modules from \s-1CPAN\s0, IO::Pty and IO::Stty.
.ie n .Sh "Is there a way to hide perl's command line from programs such as ""ps""?"
.el .Sh "Is there a way to hide perl's command line from programs such as ``ps''?"
.IX Subsection "Is there a way to hide perl's command line from programs such as ps?"
First of all note that if you're doing this for security reasons (to
avoid people seeing passwords, for example) then you should rewrite
your program so that critical information is never given as an
argument.  Hiding the arguments won't make your program completely
secure.
.PP
To actually alter the visible command line, you can assign to the
variable \f(CW$0\fR as documented in perlvar.  This won't work on all
operating systems, though.  Daemon programs like sendmail place their
state there, as in:
.PP
.Vb 1
\&    $0 = "orcus [accepting connections]";
.Ve
.Sh "I {changed directory, modified my environment} in a perl script.  How come the change disappeared when I exited the script?  How do I get my changes to be visible?"
.IX Subsection "I {changed directory, modified my environment} in a perl script.  How come the change disappeared when I exited the script?  How do I get my changes to be visible?"
.IP "Unix" 4
.IX Item "Unix"
In the strictest sense, it can't be done\*(--the script executes as a
different process from the shell it was started from.  Changes to a
process are not reflected in its parent\*(--only in any children
created after the change.  There is shell magic that may allow you to
fake it by \fIeval()\fRing the script's output in your shell; check out the
comp.unix.questions \s-1FAQ\s0 for details.
.Sh "How do I close a process's filehandle without waiting for it to complete?"
.IX Subsection "How do I close a process's filehandle without waiting for it to complete?"
Assuming your system supports such things, just send an appropriate signal
to the process (see \*(L"kill\*(R" in perlfunc).  It's common to first send a \s-1TERM\s0
signal, wait a little bit, and then send a \s-1KILL\s0 signal to finish it off.
.Sh "How do I fork a daemon process?"
.IX Subsection "How do I fork a daemon process?"
If by daemon process you mean one that's detached (disassociated from
its tty), then the following process is reported to work on most
Unixish systems.  Non-Unix users should check their Your_OS::Process
module for other solutions.
.IP "\(bu" 4
Open /dev/tty and use the \s-1TIOCNOTTY\s0 ioctl on it.  See tty
for details.  Or better yet, you can just use the \fIPOSIX::setsid()\fR
function, so you don't have to worry about process groups.
.IP "\(bu" 4
Change directory to /
.IP "\(bu" 4
Reopen \s-1STDIN\s0, \s-1STDOUT\s0, and \s-1STDERR\s0 so they're not connected to the old
tty.
.IP "\(bu" 4
Background yourself like this:
.Sp
.Vb 1
\&    fork && exit;
.Ve
.PP
The Proc::Daemon module, available from \s-1CPAN\s0, provides a function to
perform these actions for you.
.Sh "How do I find out if I'm running interactively or not?"
.IX Subsection "How do I find out if I'm running interactively or not?"
Good question.  Sometimes \f(CW\*(C`\-t STDIN\*(C'\fR and \f(CW\*(C`\-t STDOUT\*(C'\fR can give clues,
sometimes not.
.PP
.Vb 3
\&    if (-t STDIN && -t STDOUT) {
\&        print "Now what? ";
\&    }
.Ve
.PP
On \s-1POSIX\s0 systems, you can test whether your own process group matches
the current process group of your controlling terminal as follows:
.PP
.Vb 9
\&    use POSIX qw/getpgrp tcgetpgrp/;
\&    open(TTY, "/dev/tty") or die $!;
\&    $tpgrp = tcgetpgrp(fileno(*TTY));
\&    $pgrp = getpgrp();
\&    if ($tpgrp == $pgrp) {
\&        print "foreground\en";
\&    } else {
\&        print "background\en";
\&    }
.Ve
.Sh "How do I timeout a slow event?"
.IX Subsection "How do I timeout a slow event?"
Use the \fIalarm()\fR function, probably in conjunction with a signal
handler, as documented in \*(L"Signals\*(R" in perlipc and the section on
``Signals'' in the Camel.  You may instead use the more flexible
Sys::AlarmCall module available from \s-1CPAN\s0.
.PP
The \fIalarm()\fR function is not implemented on all versions of Windows.
Check the documentation for your specific version of Perl.
.Sh "How do I set \s-1CPU\s0 limits?"
.IX Subsection "How do I set CPU limits?"
Use the BSD::Resource module from \s-1CPAN\s0.
.Sh "How do I avoid zombies on a Unix system?"
.IX Subsection "How do I avoid zombies on a Unix system?"
Use the reaper code from \*(L"Signals\*(R" in perlipc to call \fIwait()\fR when a
\&\s-1SIGCHLD\s0 is received, or else use the double-fork technique described
in \*(L"How do I start a process in the background?\*(R" in perlfaq8.
.Sh "How do I use an \s-1SQL\s0 database?"
.IX Subsection "How do I use an SQL database?"
The \s-1DBI\s0 module provides an abstract interface to most database
servers and types, including Oracle, \s-1DB2\s0, Sybase, mysql, Postgresql,
\&\s-1ODBC\s0, and flat files.  The \s-1DBI\s0 module accesses each database type
through a database driver, or \s-1DBD\s0.  You can see a complete list of
available drivers on \s-1CPAN:\s0 http://www.cpan.org/modules/by\-module/DBD/ .
You can read more about \s-1DBI\s0 on http://dbi.perl.org .
.PP
Other modules provide more specific access: Win32::ODBC, Alzabo, iodbc,
and others found on \s-1CPAN\s0 Search: http://search.cpan.org .
.Sh "How do I make a \fIsystem()\fP exit on control\-C?"
.IX Subsection "How do I make a system() exit on control-C?"
You can't.  You need to imitate the \fIsystem()\fR call (see perlipc for
sample code) and then have a signal handler for the \s-1INT\s0 signal that
passes the signal on to the subprocess.  Or you can check for it:
.PP
.Vb 2
\&    $rc = system($cmd);
\&    if ($rc & 127) { die "signal death" }
.Ve
.Sh "How do I open a file without blocking?"
.IX Subsection "How do I open a file without blocking?"
If you're lucky enough to be using a system that supports
non-blocking reads (most Unixish systems do), you need only to use the
O_NDELAY or O_NONBLOCK flag from the Fcntl module in conjunction with
\&\fIsysopen()\fR:
.PP
.Vb 3
\&    use Fcntl;
\&    sysopen(FH, "/tmp/somefile", O_WRONLY|O_NDELAY|O_CREAT, 0644)
\&        or die "can't open /tmp/somefile: $!":
.Ve
.Sh "How do I install a module from \s-1CPAN\s0?"
.IX Subsection "How do I install a module from CPAN?"
The easiest way is to have a module also named \s-1CPAN\s0 do it for you.
This module comes with perl version 5.004 and later.
.PP
.Vb 1
\&    $ perl -MCPAN -e shell
.Ve
.PP
.Vb 2
\&    cpan shell -- CPAN exploration and modules installation (v1.59_54)
\&    ReadLine support enabled
.Ve
.PP
.Vb 1
\&    cpan> install Some::Module
.Ve
.PP
To manually install the \s-1CPAN\s0 module, or any well-behaved \s-1CPAN\s0 module
for that matter, follow these steps:
.IP "1" 4
.IX Item "1"
Unpack the source into a temporary area.
.IP "2" 4
.IX Item "2"
.Vb 1
\&    perl Makefile.PL
.Ve
.IP "3" 4
.IX Item "3"
.Vb 1
\&    make
.Ve
.IP "4" 4
.IX Item "4"
.Vb 1
\&    make test
.Ve
.IP "5" 4
.IX Item "5"
.Vb 1
\&    make install
.Ve
.PP
If your version of perl is compiled without dynamic loading, then you
just need to replace step 3 (\fBmake\fR) with \fBmake perl\fR and you will
get a new \fIperl\fR binary with your extension linked in.
.PP
See ExtUtils::MakeMaker for more details on building extensions.
See also the next question, ``What's the difference between require
and use?''.
.Sh "What's the difference between require and use?"
.IX Subsection "What's the difference between require and use?"
Perl offers several different ways to include code from one file into
another.  Here are the deltas between the various inclusion constructs:
.PP
.Vb 3
\&    1)  do $file is like eval `cat $file`, except the former
\&        1.1: searches @INC and updates %INC.
\&        1.2: bequeaths an *unrelated* lexical scope on the eval'ed code.
.Ve
.PP
.Vb 3
\&    2)  require $file is like do $file, except the former
\&        2.1: checks for redundant loading, skipping already loaded files.
\&        2.2: raises an exception on failure to find, compile, or execute $file.
.Ve
.PP
.Vb 3
\&    3)  require Module is like require "Module.pm", except the former
\&        3.1: translates each "::" into your system's directory separator.
\&        3.2: primes the parser to disambiguate class Module as an indirect object.
.Ve
.PP
.Vb 3
\&    4)  use Module is like require Module, except the former
\&        4.1: loads the module at compile time, not run-time.
\&        4.2: imports symbols and semantics from that package to the current one.
.Ve
.PP
In general, you usually want \f(CW\*(C`use\*(C'\fR and a proper Perl module.
.Sh "How do I keep my own module/library directory?"
.IX Subsection "How do I keep my own module/library directory?"
When you build modules, use the \s-1PREFIX\s0 and \s-1LIB\s0 options when generating
Makefiles:
.PP
.Vb 1
\&    perl Makefile.PL PREFIX=/mydir/perl LIB=/mydir/perl/lib
.Ve
.PP
then either set the \s-1PERL5LIB\s0 environment variable before you run
scripts that use the modules/libraries (see perlrun) or say
.PP
.Vb 1
\&    use lib '/mydir/perl/lib';
.Ve
.PP
This is almost the same as
.PP
.Vb 3
\&    BEGIN {
\&        unshift(@INC, '/mydir/perl/lib');
\&    }
.Ve
.PP
except that the lib module checks for machine-dependent subdirectories.
See Perl's lib for more information.
.Sh "How do I add the directory my program lives in to the module/library search path?"
.IX Subsection "How do I add the directory my program lives in to the module/library search path?"
.Vb 3
\&    use FindBin;
\&    use lib "$FindBin::Bin";
\&    use your_own_modules;
.Ve
.Sh "How do I add a directory to my include path (@INC) at runtime?"
.IX Subsection "How do I add a directory to my include path (@INC) at runtime?"
Here are the suggested ways of modifying your include path:
.PP
.Vb 5
\&    the PERLLIB environment variable
\&    the PERL5LIB environment variable
\&    the perl -Idir command line flag
\&    the use lib pragma, as in
\&        use lib "$ENV{HOME}/myown_perllib";
.Ve
.PP
The latter is particularly useful because it knows about machine
dependent architectures.  The lib.pm pragmatic module was first
included with the 5.002 release of Perl.
.Sh "What is socket.ph and where do I get it?"
.IX Subsection "What is socket.ph and where do I get it?"
It's a perl4\-style file defining values for system networking
constants.  Sometimes it is built using h2ph when Perl is installed,
but other times it is not.  Modern programs \f(CW\*(C`use Socket;\*(C'\fR instead.
.SH "AUTHOR AND COPYRIGHT"
.IX Header "AUTHOR AND COPYRIGHT"
Copyright (c) 1997\-2003 Tom Christiansen and Nathan Torkington.
All rights reserved.
.PP
This documentation is free; you can redistribute it and/or modify it
under the same terms as Perl itself.
.PP
Irrespective of its distribution, all code examples in this file
are hereby placed into the public domain.  You are permitted and
encouraged to use this code in your own programs for fun
or for profit as you see fit.  A simple comment in the code giving
credit would be courteous but is not required.