CGI::Session::Driver::file man page on Oracle

Man page or keyword search:  
man Server   33470 pages
apropos Keyword Search (all sections)
Output format
Oracle logo
[printable version]

CGI::Session::Driver::User(Contributed Perl DocumCGI::Session::Driver::file(3)

       CGI::Session::Driver::file - Default CGI::Session driver

	   $s = new CGI::Session();
	   $s = new CGI::Session("driver:file", $sid);
	   $s = new CGI::Session("driver:file", $sid, {Directory=>'/tmp'});

       When CGI::Session object is created without explicitly setting driver,
       file will be assumed.  file - driver will store session data in plain
       files, where each session will be stored in a separate file.

       Naming conventions of session files are defined by
       $CGI::Session::Driver::file::FileName global variable.  Default value
       of this variable is cgisess_%s, where %s will be replaced with
       respective session ID. Should you wish to set your own FileName
       template, do so before requesting for session object:

	   use CGI::Session::Driver::file; # This line is mandatory.
	   # Time passes...
	   $CGI::Session::Driver::file::FileName = "%s.dat";
	   $s = new CGI::Session();

       For backwards compatibility with 3.x, you can also use the variable
       name $CGI::Session::File::FileName, which will override the one above.

       If you wish to specify a session directory, use the Directory option,
       which denotes location of the directory where session ids are to be
       kept. If Directory is not set, defaults to whatever
       File::Spec->tmpdir() returns.  So all the three lines in the SYNOPSIS
       section of this manual produce the same result on a UNIX machine.

       If specified Directory does not exist, all necessary directory
       hierarchy will be created.

       By default, sessions are created with a umask of 0660. If you wish to
       change the umask for a session, pass a UMask option with an octal
       representation of the umask you would like for said session.

       If your OS doesn't support flock, you should understand the risks of
       going without locking the session files. Since sessions tend to be used
       in environments where race conditions may occur due to concurrent
       access of files by different processes, locking tends to be seen as a
       good and very necessary thing. If you still want to use this driver but
       don't want flock, set $CGI::Session::Driver::file::NoFlock to 1 or pass
       "NoFlock => 1" and this driver will operate without locks.

       For support and licensing see CGI::Session

perl v5.16.3			  2008-07-15	 CGI::Session::Driver::file(3)

List of man pages available for Oracle

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net