Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
International Rescue Committe

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 67 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       perl [ -sTtuUWX ]      [ -hv ] [ -V[:configvar] ]
            [ -cw ] [ -d[:debugger] ] [ -D[number/list] ]
            [ -pna ] [ -Fpattern ] [ -l[octal] ] [ -0[octal/hex­
       adecimal] ]      [ -Idir ] [ -m[-]module ] [ -M[-]'mod­
       ule...' ]      [ -P ]      [ -S ]      [ -x[dir] ]
            [ -i[extension] ]      [ -e 'command' ] [ -- ] [ pro­
       gramfile ] [ argument ]...       [ -C [nnuummbbeerr//lliisstt] ] ]>


       The normal way to run a Perl program is by making it
       directly executable, or else by passing the name of the
       source file as an argument on the command line.  (An
       interactive Perl environment is also possible--see perlde­
       bug for details on how to do that.)  Upon startup, Perl
       looks for your program in one of the following places:

       1.  Specified line by line via -e switches on the command

       2.  Contained in the file specified by the first filename
           on the command line.  (Note that systems supporting
           the #! notation invoke interpreters this way. See
           "Location of Perl".)

       3.  Passed in implicitly via standard input.  This works
           only if there are no filename arguments--to pass argu­
           ments to a STDIN-read program you must explicitly
           specify a "-" for the program name.

       With methods 2 and 3, Perl starts parsing the input file
       from the beginning, unless you've specified a -x switch,
       in which case it scans for the first line starting with #!
       and containing the word "perl", and starts there instead.
       This is useful for running a program embedded in a larger
       message.  (In this case you would indicate the end of the
       program using the "__END__" token.)

       The #! line is always examined for switches as the line is
       being parsed.  Thus, if you're on a machine that allows
       only one argument with the #! line, or worse, doesn't even
       recognize the #! line, you still can get consistent switch
       behavior regardless of how Perl was invoked, even if -x
       was used to find the beginning of the program.

       Because historically some operating systems silently
       chopped off kernel interpretation of the #! line after 32
       characters, some switches may be passed in on the command
       line, and some may not; you could even get a "-" without
       its letter, if you're not careful.  You probably want to
       make sure that all your switches fall either before or
       after that 32-character boundary.  Most switches don't
       inclined, say

           #!/bin/sh -- # -*- perl -*- -p
           eval 'exec perl -wS $0 ${1+"$@"}'
               if $running_under_some_shell;

       to let Perl see the -p switch.

       A similar trick involves the env program, if you have it.

           #!/usr/bin/env perl

       The examples above use a relative path to the perl inter­
       preter, getting whatever version is first in the user's
       path.  If you want a specific version of Perl, say,
       perl5.005_57, you should place that directly in the #!
       line's path.

       If the #! line does not contain the word "perl", the pro­
       gram named after the #! is executed instead of the Perl
       interpreter.  This is slightly bizarre, but it helps peo­
       ple on machines that don't do #!, because they can tell a
       program that their SHELL is /usr/bin/perl, and Perl will
       then dispatch the program to the correct interpreter for

       After locating your program, Perl compiles the entire pro­
       gram to an internal form.  If there are any compilation
       errors, execution of the program is not attempted.  (This
       is unlike the typical shell script, which might run part-
       way through before finding a syntax error.)

       If the program is syntactically correct, it is executed.
       If the program runs off the end without hitting an exit()
       or die() operator, an implicit exit(0) is provided to
       indicate successful completion.

       #! and quoting on non-Unix systems

       Unix's #! technique can be simulated on other systems:


               extproc perl -S -your_switches

           as the first line in "*.cmd" file (-S due to a bug in
           cmd.exe's `extproc' handling).

           Create a batch file to run your program, and codify it
           in "ALTERNATE_SHEBANG" (see the dosish.h file in the
           Creator and Type, so that double-clicking them will
           invoke the perl application.

       VMS Put

               $ perl -mysw 'f$env("procedure")' 'p1' 'p2' 'p3' 'p4' 'p5' 'p6' 'p7' 'p8' !
               $ exit++ + ++$status != 0 and $exit = $status = undef;

           at the top of your program, where -mysw are any com­
           mand line switches you want to pass to Perl.  You can
           now invoke the program directly, by saying "perl pro­
           gram", or as a DCL procedure, by saying @program (or
           implicitly via DCL$PATH by just using the name of the

           This incantation is a bit much to remember, but Perl
           will display it for you if you say "perl "-V:start­

       Command-interpreters on non-Unix systems have rather dif­
       ferent ideas on quoting than Unix shells.  You'll need to
       learn the special characters in your command-interpreter
       ("*", "\" and """ are common) and how to protect whites­
       pace and these characters to run one-liners (see -e

       On some systems, you may have to change single-quotes to
       double ones, which you must not do on Unix or Plan 9 sys­
       tems.  You might also have to change a single % to a %%.

       For example:

           # Unix
           perl -e 'print "Hello world\n"'

           # MS-DOS, etc.
           perl -e "print \"Hello world\n\""

           # Macintosh
           print "Hello world\n"
            (then Run "Myscript" or Shift-Command-R)

           # VMS
           perl -e "print ""Hello world\n"""

       The problem is that none of this is reliable: it depends
       on the command and it is entirely possible neither works.
       If 4DOS were the command shell, this would probably work

           perl -e "print <Ctrl-x>"Hello world\n<Ctrl-x>""

       It may seem obvious to say, but Perl is useful only when
       users can easily find it.  When possible, it's good for
       both /usr/bin/perl and /usr/local/bin/perl to be symlinks
       to the actual binary.  If that can't be done, system
       administrators are strongly encouraged to put (symlinks
       to) perl and its accompanying utilities into a directory
       typically found along a user's PATH, or in some other
       obvious and convenient place.

       In this documentation, "#!/usr/bin/perl" on the first line
       of the program will stand in for whatever method works on
       your system.  You are advised to use a specific path if
       you care about a specific version.


       or if you just want to be running at least version, place
       a statement like this at the top of your program:

           use 5.005_54;

       Command Switches

       As with all standard commands, a single-character switch
       may be clustered with the following switch, if any.

           #!/usr/bin/perl -spi.orig   # same as -s -p -i.orig

       Switches include:

            specifies the input record separator ($/) as an octal
            or hexadecimal number.  If there are no digits, the
            null character is the separator.  Other switches may
            precede or follow the digits.  For example, if you
            have a version of find which can print filenames ter­
            minated by the null character, you can say this:

                find . -name '*.orig' -print0 | perl -n0e unlink

            The special value 00 will cause Perl to slurp files
            in paragraph mode.  The value 0777 will cause Perl to
            slurp files whole because there is no legal byte with
            that value.

            If you want to specify any Unicode character, use the
            hexadecimal format: "-0xHHH...", where the "H" are
            valid hexadecimal digits.  (This means that you can­
            not use the "-x" with a directory name that consists
            of hexadecimal digits.)

            An alternate delimiter may be specified using -F.

       -C [nnuummbbeerr//lliisstt]
            The "-C" flag controls some Unicode of the Perl Uni­
            code features.

            As of 5.8.1, the "-C" can be followed either by a
            number or a list of option letters.  The letters,
            their numeric values, and effects are as follows;
            listing the letters is equal to summing the numbers.

                I     1    STDIN is assumed to be in UTF-8
                O     2    STDOUT will be in UTF-8
                E     4    STDERR will be in UTF-8
                S     7    I + O + E
                i     8    UTF-8 is the default PerlIO layer for input streams
                o    16    UTF-8 is the default PerlIO layer for output streams
                D    24    i + o
                A    32    the @ARGV elements are expected to be strings encoded in UTF-8
                L    64    normally the "IOEioA" are unconditional,
                           the L makes them conditional on the locale environment
                           variables (the LC_ALL, LC_TYPE, and LANG, in the order
                           of decreasing precedence) -- if the variables indicate
                           UTF-8, then the selected "IOEioA" are in effect

            For example, "-COE" and "-C6" will both turn on
            UTF-8-ness on both STDOUT and STDERR.  Repeating let­
            ters is just redundant, not cumulative nor toggling.

            The "io" options mean that any subsequent open() (or
            similar I/O operations) will have the ":utf8" PerlIO
            layer implicitly applied to them, in other words,
            UTF-8 is expected from any input stream, and UTF-8 is
            produced to any output stream.  This is just the
            default, with explicit layers in open() and with bin­
            mode() one can manipulate streams as usual.

            "-C" on its own (not followed by any number or option
            list), or the empty string "" for the "$ENV{PERL_UNI­
            CODE}, has the same effect as <-CSDL".  In other
            words, the standard I/O handles and the default
            "open()" layer are UTF-8-fied but only if the locale
            environment variables indicate a UTF-8 locale.  This
            behaviour follows the implicit (and problematic)
            UTF-8 behaviour of Perl 5.8.0.

            You can use "-C0" (or "0" for $ENV{PERL_UNICODE}) to
            explicitly disable all the above Unicode features.

            The read-only magic variable "${^UNICODE}" reflects
            the numeric value of this setting.  This is variable
            is set during Perl startup and is thereafter
            these are considered as occurring outside the execu­
            tion of your program.  "INIT" and "END" blocks, how­
            ever, will be skipped.

       -d   runs the program under the Perl debugger.  See

            runs the program under the control of a debugging,
            profiling, or tracing module installed as Devel::foo.
            E.g., -d:DProf executes the program using the
            Devel::DProf profiler.  As with the -M flag, options
            may be passed to the Devel::foo package where they
            will be received and interpreted by the
            Devel::foo::import routine.  The comma-separated list
            of options must follow a "=" character.  See perlde­

            sets debugging flags.  To watch how it executes your
            program, use -Dtls.  (This works only if debugging is
            compiled into your Perl.)  Another nice value is -Dx,
            which lists your compiled syntax tree.  And -Dr dis­
            plays compiled regular expressions; the format of the
            output is explained in perldebguts.

            As an alternative, specify a number instead of list
            of letters (e.g., -D14 is equivalent to -Dtls):

                    1  p  Tokenizing and parsing
                    2  s  Stack snapshots
                            with v, displays all stacks
                    4  l  Context (loop) stack processing
                    8  t  Trace execution
                   16  o  Method and overloading resolution
                   32  c  String/numeric conversions
                   64  P  Print profiling info, preprocessor command for -P, source file input state
                  128  m  Memory allocation
                  256  f  Format processing
                  512  r  Regular expression parsing and execution
                 1024  x  Syntax tree dump
                 2048  u  Tainting checks
                 4096     (Obsolete, previously used for LEAKTEST)
                 8192  H  Hash dump -- usurps values()
                16384  X  Scratchpad allocation
                32768  D  Cleaning up
                65536  S  Thread synchronization
               131072  T  Tokenising
               262144  R  Include reference counts of dumped variables (eg when using -Ds)
               524288  J  Do not s,t,P-debug (Jump over) opcodes within package DB
              1048576  v  Verbose: use in conjunction with other flags
              # If you have "env" utility
              env=PERLDB_OPTS="NonStop=1 AutoTrace=1 frame=2" perl -dS program

              # Bourne shell syntax
              $ PERLDB_OPTS="NonStop=1 AutoTrace=1 frame=2" perl -dS program

              # csh syntax
              % (setenv PERLDB_OPTS "NonStop=1 AutoTrace=1 frame=2"; perl -dS program)

            See perldebug for details and variations.

       -e commandline
            may be used to enter one line of program.  If -e is
            given, Perl will not look for a filename in the argu­
            ment list.  Multiple -e commands may be given to
            build up a multi-line script.  Make sure to use semi­
            colons where you would in a normal program.

            specifies the pattern to split on if -a is also in
            effect.  The pattern may be surrounded by "//", "",
            or '', otherwise it will be put in single quotes.

       -h   prints a summary of the options.

            specifies that files processed by the "<>" construct
            are to be edited in-place.  It does this by renaming
            the input file, opening the output file by the origi­
            nal name, and selecting that output file as the
            default for print() statements.  The extension, if
            supplied, is used to modify the name of the old file
            to make a backup copy, following these rules:

            If no extension is supplied, no backup is made and
            the current file is overwritten.

            If the extension doesn't contain a "*", then it is
            appended to the end of the current filename as a suf­
            fix.  If the extension does contain one or more "*"
            characters, then each "*" is replaced with the cur­
            rent filename.  In Perl terms, you could think of
            this as:

                ($backup = $extension) =~ s/\*/$file_name/g;

            This allows you to add a prefix to the backup file,
            instead of (or in addition to) a suffix:

                $ perl -pi 'orig_*' -e 's/bar/baz/' fileA   # backup to 'orig_fileA'

            Or even to place backup copies of the original files

                $ perl -p -i.orig -e "s/foo/bar/; ... "

            is the same as using the program:

                #!/usr/bin/perl -pi.orig

            which is equivalent to

                $extension = '.orig';
                LINE: while (<>) {
                    if ($ARGV ne $oldargv) {
                        if ($extension !~ /\*/) {
                            $backup = $ARGV . $extension;
                        else {
                            ($backup = $extension) =~ s/\*/$ARGV/g;
                        rename($ARGV, $backup);
                        open(ARGVOUT, ">$ARGV");
                        $oldargv = $ARGV;
                continue {
                    print;  # this prints to original filename

            except that the -i form doesn't need to compare $ARGV
            to $oldargv to know when the filename has changed.
            It does, however, use ARGVOUT for the selected file­
            handle.  Note that STDOUT is restored as the default
            output filehandle after the loop.

            As shown above, Perl creates the backup file whether
            or not any output is actually changed.  So this is
            just a fancy way to copy files:

                $ perl -p -i'/some/file/path/*' -e 1 file1 file2 file3...
                $ perl -p -i'.orig' -e 1 file1 file2 file3...

            You can use "eof" without parentheses to locate the
            end of each input file, in case you want to append to
            each file, or reset line numbering (see example in
            "eof" in perlfunc).

            If, for a given file, Perl is unable to create the

                $ perl -pi~ -e 's/foo/bar/' file1 file2 file3...

            Finally, the -i switch does not impede execution when
            no files are given on the command line.  In this
            case, no backup is made (the original file cannot, of
            course, be determined) and processing proceeds from
            STDIN to STDOUT as might be expected.

            Directories specified by -I are prepended to the
            search path for modules (@INC), and also tells the C
            preprocessor where to search for include files.  The
            C preprocessor is invoked with -P; by default it
            searches /usr/include and /usr/lib/perl.

            enables automatic line-ending processing.  It has two
            separate effects.  First, it automatically chomps $/
            (the input record separator) when used with -n or -p.
            Second, it assigns "$\" (the output record separator)
            to have the value of octnum so that any print state­
            ments will have that separator added back on.  If
            octnum is omitted, sets "$\" to the current value of
            $/.  For instance, to trim lines to 80 columns:

                perl -lpe 'substr($_, 80) = ""'

            Note that the assignment "$\ = $/" is done when the
            switch is processed, so the input record separator
            can be different than the output record separator if
            the -l switch is followed by a -0 switch:

                gnufind / -print0 | perl -ln0e 'print "found $_" if -p'

            This sets "$\" to newline and then sets $/ to the
            null character.

       -M[-]'module ...'
            -mmodule executes "use" module "();" before executing
            your program.

            -Mmodule executes "use" module ";" before executing
            your program.  You can use quotes to add extra code
            after the module name, e.g., '-Mmodule qw(foo bar)'.

            If the first character after the -M or -m is a dash
            ("-") then the 'use' is replaced with 'no'.

                    ...             # your program goes here

            Note that the lines are not printed by default.  See
            -p to have lines printed.  If a file named by an
            argument cannot be opened for some reason, Perl warns
            you about it and moves on to the next file.

            Here is an efficient way to delete all files older
            than a week:

                find . -mtime +7 -print | perl -nle unlink

            This is faster than using the -exec switch of find
            because you don't have to start a process on every
            filename found.  It does suffer from the bug of mis­
            handling newlines in pathnames, which you can fix if
            you follow the example under -0.

            "BEGIN" and "END" blocks may be used to capture con­
            trol before or after the implicit program loop, just
            as in awk.

       -p   causes Perl to assume the following loop around your
            program, which makes it iterate over filename argu­
            ments somewhat like sed:

                while (<>) {
                    ...             # your program goes here
                } continue {
                    print or die "-p destination: $!\n";

            If a file named by an argument cannot be opened for
            some reason, Perl warns you about it, and moves on to
            the next file.  Note that the lines are printed auto­
            matically.  An error occurring during printing is
            treated as fatal.  To suppress printing use the -n
            switch.  A -p overrides a -n switch.

            "BEGIN" and "END" blocks may be used to capture con­
            trol before or after the implicit loop, just as in

       -P   NOTE: Use of -P is strongly discouraged because of
            its inherent problems, including poor portability.

            This option causes your program to be run through the
            C preprocessor before compilation by Perl.  Because
            both comments and cpp directives begin with the #
            character, you should avoid starting comments with
                      a "#" but do not look like cpp commands,
                      are stripped, including anything inside
                      Perl strings, regular expressions, and
                      here-docs .

            *         In some platforms the C preprocessor knows
                      too much: it knows about the C++ -style
                      until-end-of-line comments starting with
                      "//".  This will cause problems with common
                      Perl constructs like


                      because after -P this will became illegal


                      The workaround is to use some other quoting
                      separator than "/", like for example "!":


            *         It requires not only a working C preproces­
                      sor but also a working sed.  If not on
                      UNIX, you are probably out of luck on this.

            *         Script line numbers are not preserved.

            *         The "-x" does not work with "-P".

       -s   enables rudimentary switch parsing for switches on
            the command line after the program name but before
            any filename arguments (or before an argument of --).
            This means you can have switches with two leading
            dashes (--help).  Any switch found there is removed
            from @ARGV and sets the corresponding variable in the
            Perl program.  The following program prints "1" if
            the program is invoked with a -xyz switch, and "abc"
            if it is invoked with -xyz=abc.

                #!/usr/bin/perl -s
                if ($xyz) { print "$xyz\n" }

            Do note that --help creates the variable ${-help},
            which is not compliant with "strict refs".

       -S   makes Perl use the PATH environment variable to
            search for the program (unless the name of the pro­
            gram contains directory separators).

            On some platforms, this also makes Perl append suf­
                eval 'exec /usr/bin/perl -wS $0 ${1+"$@"}'
                        if $running_under_some_shell;

            The system ignores the first line and feeds the pro­
            gram to /bin/sh, which proceeds to try to execute the
            Perl program as a shell script.  The shell executes
            the second line as a normal shell command, and thus
            starts up the Perl interpreter.  On some systems $0
            doesn't always contain the full pathname, so the -S
            tells Perl to search for the program if necessary.
            After Perl locates the program, it parses the lines
            and ignores them because the variable $run­
            ning_under_some_shell is never true.  If the program
            will be interpreted by csh, you will need to replace
            "${1+"$@"}" with $*, even though that doesn't under­
            stand embedded spaces (and such) in the argument
            list.  To start up sh rather than csh, some systems
            may have to replace the #! line with a line contain­
            ing just a colon, which will be politely ignored by
            Perl.  Other systems can't control that, and need a
            totally devious construct that will work under any of
            csh, sh, or Perl, such as the following:

                    eval '(exit $?0)' && eval 'exec perl -wS $0 ${1+"$@"}'
                    & eval 'exec /usr/bin/perl -wS $0 $argv:q'
                            if $running_under_some_shell;

            If the filename supplied contains directory separa­
            tors (i.e., is an absolute or relative pathname), and
            if that file is not found, platforms that append file
            extensions will do so and try to look for the file
            with those extensions added, one by one.

            On DOS-like platforms, if the program does not con­
            tain directory separators, it will first be searched
            for in the current directory before being searched
            for on the PATH.  On Unix platforms, the program will
            be searched for strictly on the PATH.

       -t   Like -T, but taint checks will issue warnings rather
            than fatal errors.  These warnings can be controlled
            normally with "no warnings qw(taint)".

            NOTE: this is not a substitute for -T. This is meant
            only to be used as a temporary development aid while
            securing legacy code: for real production code and
            for new secure code written from scratch always use
            the real -T.

       -T   forces "taint" checks to be turned on so you can test
            them.  Ordinarily these checks are done only when
            running setuid or setgid.  It's a good idea to turn
            can minimize by stripping the executable).  (Still, a
            "hello world" executable comes out to about 200K on
            my machine.)  If you want to execute a portion of
            your program before dumping, use the dump() operator
            instead.  Note: availability of undump is platform
            specific and may not be available for a specific port
            of Perl.

            This switch has been superseded in favor of the new
            Perl code generator backends to the compiler.  See B
            and B::Bytecode for details.

       -U   allows Perl to do unsafe operations.  Currently the
            only "unsafe" operations are the unlinking of direc­
            tories while running as superuser, and running setuid
            programs with fatal taint checks turned into warn­
            ings.  Note that the -w switch (or the $^W variable)
            must be used along with this option to actually gen­
            erate the taint-check warnings.

       -v   prints the version and patchlevel of your perl exe­

       -V   prints summary of the major perl configuration values
            and the current values of @INC.

            Prints to STDOUT the value of the named configuration
            variable.  For example,

                $ perl -V:man.dir

            will provide strong clues about what your MANPATH
            variable should be set to in order to access the Perl

       -w   prints warnings about dubious constructs, such as
            variable names that are mentioned only once and
            scalar variables that are used before being set,
            redefined subroutines, references to undefined file­
            handles or filehandles opened read-only that you are
            attempting to write on, values used as a number that
            doesn't look like numbers, using an array as though
            it were a scalar, if your subroutines recurse more
            than 100 deep, and innumerable other things.

            This switch really just enables the internal $^W
            variable.  You can disable or promote into fatal
            errors specific warnings using "__WARN__" hooks, as
            described in perlvar and "warn" in perlfunc.  See
            also perldiag and perltrap.  A new, fine-grained
            warning facility is also available if you want to
            string "perl".  Any meaningful switches on that line
            will be applied.  If a directory name is specified,
            Perl will switch to that directory before running the
            program.  The -x switch controls only the disposal of
            leading garbage.  The program must be terminated with
            "__END__" if there is trailing garbage to be ignored
            (the program can process any or all of the trailing
            garbage via the DATA filehandle if desired).


       HOME        Used if chdir has no argument.

       LOGDIR      Used if chdir has no argument and HOME is not

       PATH        Used in executing subprocesses, and in finding
                   the program if -S is used.

       PERL5LIB    A list of directories in which to look for
                   Perl library files before looking in the stan­
                   dard library and the current directory.  Any
                   architecture-specific directories under the
                   specified locations are automatically included
                   if they exist.  If PERL5LIB is not defined,
                   PERLLIB is used.  Directories are separated
                   (like in PATH) by a colon on unixish platforms
                   and by a semicolon on Windows (the proper path
                   separator being given by the command "perl

                   When running taint checks (either because the
                   program was running setuid or setgid, or the
                   -T switch was used), neither variable is used.
                   The program should instead say:

                       use lib "/my/directory";

       PERL5OPT    Command-line options (switches).  Switches in
                   this variable are taken as if they were on
                   every Perl command line.  Only the -[DIMUdmtw]
                   switches are allowed.  When running taint
                   checks (because the program was running setuid
                   or setgid, or the -T switch was used), this
                   variable is ignored.  If PERL5OPT begins with
                   -T, tainting will be enabled, and any subse­
                   quent options ignored.

       PERLIO      A space (or colon) separated list of PerlIO
                   layers. If perl is built to use PerlIO system
                   for IO (the default) these layers effect
                   perl's IO.

                   them!. See "open pragma" for how to add exter­
                   nal encodings as defaults.

                   The layers that it makes sense to include in
                   the PERLIO environment variable are summarised
                   below. For more details see PerlIO.

                   :bytes  A pseudolayer that turns off the
                           ":utf8" flag for the layer below.
                           Unlikely to be useful on its own in
                           the global PERLIO environment vari­
                           able.  You perhaps were thinking of
                           ":crlf:bytes" or ":perlio:bytes".

                   :crlf   A layer that implements DOS/Windows
                           like CRLF line endings.  On read con­
                           verts pairs of CR,LF to a single "\n"
                           newline character.  On write converts
                           each "\n" to a CR,LF pair.  Note that
                           this layer likes to be one of its
                           kind: it silently ignores attempts to
                           be pushed into the layer stack more
                           than once.

                           (Gory details follow) To be more exact
                           what happens is this: after pushing
                           itself to the stack, the ":crlf" layer
                           checks all the layers below itself to
                           find the first layer that is capable
                           of being a CRLF layer but is not yet
                           enabled to be a CRLF layer.  If it
                           finds such a layer, it enables the
                           CRLFness of that other deeper layer,
                           and then pops itself off the stack.
                           If not, fine, use the one we just

                           The end result is that a ":crlf" means
                           "please enable the first CRLF layer
                           you can find, and if you can't find
                           one, here would be a good spot to
                           place a new one."

                           Based on the ":perlio" layer.

                   :mmap   A layer which implements "reading" of
                           files by using "mmap()" to make
                           (whole) file appear in the process's
                           address space, and then using that as
                           PerlIO's "buffer". This may be faster
                           in certain circumstances for large
                           files, and may result in less physical
                           buffering for PerlIO. Provides fast
                           access to the buffer for "sv_gets"
                           which implements perl's readline/<>
                           and in general attempts to minimize
                           data copying.

                           ":perlio" will insert a ":unix" layer
                           below itself to do low level IO.

                   :pop    An experimental pseudolayer that
                           removes the topmost layer.  Use with
                           the same care as is reserved for

                   :raw    A pseudolayer that manipulates other
                           layers.  Applying the <:raw> layer is
                           equivalent to calling "binmode($fh)".
                           It makes the stream pass each byte as-
                           is without any translation.  In par­
                           ticular CRLF translation, and/or :utf8
                           intuited from locale are disabled.

                           Arranges for all accesses go straight
                           to the lowest buffered layer provided
                           by the configration. That is it strips
                           off any layers above that layer.

                           In Perl 5.6 and some books the ":raw"
                           layer (previously sometimes also
                           referred to as a "discipline") is doc­
                           umented as the inverse of the ":crlf"
                           layer. That is no longer the case -
                           other layers which would alter binary
                           nature of the stream are also dis­
                           abled.  If you want UNIX line endings
                           on a platform that normally does CRLF
                           translation, but still want UTF-8 or
                           encoding defaults the appropriate
                           thing to do is to add ":perlio" to
                           PERLIO environment variable.

                   :stdio  This layer provides PerlIO interface
                           by wrapping system's ANSI C "stdio"
                           library calls. The layer provides both
                           buffering and IO.  Note that ":stdio"
                           layer does not do CRLF translation
                           even if that is platforms normal
                           behaviour. You will need a ":crlf"
                           layer above it to do that.

                   :unix   Lowest level layer which provides
                           basic PerlIO operations in terms of
                           off that behaviour use ":bytes"

                   :win32  On Win32 platforms this experimental
                           layer uses native "handle" IO rather
                           than unix-like numeric file descriptor
                           layer. Known to be buggy in this

                   On all platforms the default set of layers
                   should give acceptable results.

                   For UNIX platforms that will equivalent of
                   "unix perlio" or "stdio".  Configure is setup
                   to prefer "stdio" implementation if system's
                   library provides for fast access to the
                   buffer, otherwise it uses the "unix perlio"

                   On Win32 the default in this release is "unix
                   crlf". Win32's "stdio" has a number of
                   bugs/mis-features for perl IO which are some­
                   what C compiler vendor/version dependent.
                   Using our own "crlf" layer as the buffer
                   avoids those issues and makes things more uni­
                   form.  The "crlf" layer provides CRLF to/from
                   "\n" conversion as well as buffering.

                   This release uses "unix" as the bottom layer
                   on Win32 and so still uses C compiler's
                   numeric file descriptor routines. There is an
                   experimental native "win32" layer which is
                   expected to be enhanced and should eventually
                   replace the "unix" layer.

                   If set to the name of a file or device then
                   certain operations of PerlIO sub-system will
                   be logged to that file (opened as append).
                   Typical uses are UNIX:

                      PERLIO_DEBUG=/dev/tty perl script ...

                   and Win32 approximate equivalent:

                      set PERLIO_DEBUG=CON
                      perl script ...

       PERLLIB     A list of directories in which to look for
                   Perl library files before looking in the stan­
                   dard library and the current directory.  If
                   PERL5LIB is defined, PERLLIB is not used.
                   slash) with a backslash.

                   Note that Perl doesn't use COMSPEC for this
                   purpose because COMSPEC has a high degree of
                   variability among users, leading to portabil­
                   ity concerns.  Besides, perl can use a shell
                   that may not be fit for interactive use, and
                   setting COMSPEC to such a shell may interfere
                   with the proper functioning of other programs
                   (which usually look in COMSPEC to find a shell
                   fit for interactive use).

                   Relevant only if perl is compiled with the
                   malloc included with the perl distribution
                   (that is, if "perl -V:d_mymalloc" is
                   'define').  If set, this causes memory statis­
                   tics to be dumped after execution.  If set to
                   an integer greater than one, also causes mem­
                   ory statistics to be dumped after compilation.

                   Relevant only if your perl executable was
                   built with -DDEBUGGING, this controls the
                   behavior of global destruction of objects and
                   other references.  See "PERL_DESTRUCT_LEVEL"
                   in perlhack for more information.

                   If using the "encoding" pragma without an
                   explicit encoding name, the PERL_ENCODING
                   environment variable is consulted for an
                   encoding name.

                   (Since Perl 5.8.1.)  Used to randomise Perl's
                   internal hash function.  To emulate the
                   pre-5.8.1 behaviour, set to an integer (zero
                   means exactly the same order as 5.8.0).
                   "Pre-5.8.1" means, among other things, that
                   hash keys will be ordered the same between
                   different runs of Perl.

                   The default behaviour is to randomise unless
                   the PERL_HASH_SEED is set.  If Perl has been
                   compiled with "-DUSE_HASH_SEED_EXPLICIT", the
                   default behaviour is not to randomise unless
                   the PERL_HASH_SEED is set.

                   If PERL_HASH_SEED is unset or set to a non-
                   numeric string, Perl uses the pseudorandom
                   seed supplied by the operating system and

                   (Since Perl 5.8.1.)  Set to one to display (to
                   STDERR) the value of the hash seed at the
                   beginning of execution.  This, combined with
                   "PERL_HASH_SEED" is intended to aid in debug­
                   ging nondeterministic behavior caused by hash

                   Note that the hash seed is sensitive informa­
                   tion: by knowing it one can craft a denial-of-
                   service attack against Perl code, even
                   remotely, see "Algorithmic Complexity Attacks"
                   in perlsec for more information.  Do not dis­
                   close the hash seed to people who don't need
                   to know it.  See also hash_seed() of

       PERL_ROOT (specific to the VMS port)
                   A translation concealed rooted logical name
                   that contains perl and the logical device for
                   the @INC path on VMS only.  Other logical
                   names that affect perl on VMS include PERLSHR,
                   but are optional and discussed further in per­
                   lvms and in README.vms in the Perl source dis­

                   In Perls 5.8.1 and later.  If set to "unsafe"
                   the pre-Perl-5.8.0 signals behaviour (immedi­
                   ate but unsafe) is restored.  If set to "safe"
                   the safe (or deferred) signals are used.  See
                   "Deferred Signals (Safe signals)" in perlipc.

                   Equivalent to the -C command-line switch.
                   Note that this is not a boolean variable--
                   setting this to "1" is not the right way to
                   "enable Unicode" (whatever that would mean).
                   You can use "0" to "disable Unicode", though
                   (or alternatively unset PERL_UNICODE in your
                   shell before starting Perl).  See the descrip­
                   tion of the "-C" switch for more information.

       SYS$LOGIN (specific to the VMS port)
                   Used if chdir has no argument and HOME and
                   LOGDIR are not set.

       Perl also has environment variables that control how Perl
       handles data specific to particular natural languages.
       See perllocale.

Help us cut cost by not downloading the whole site!
Use of automated download sofware ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and therefore is expressedly prohibited. For more details on this, take a look here



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.11 Seconds