DACS 1.4.19 Single Sign-On System Released - CGI Directory (press release)

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News DACS 1.4.19 Single Sign-On System Released - CGI Directory (press release)
# 1  
Old 07-06-2007
DACS 1.4.19 Single Sign-On System Released - CGI Directory (press release)

DACS 1.4.19 Single Sign-On System Released
CGI Directory (press release), IL - 13 minutes ago
... an Apache 2.0/2.2 module, suite of CGI programs, and collection of command line tools for Unix-type platforms, such as GNU/Linux, FreeBSD, and Solaris. ...

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to detect key press in cgi shell script?

I want to detect key pressed in my .cgi web page, but it does not work even I found the code in other web site. My code is : #!/bin/sh #================================================= # PATH defination # ================================================... (2 Replies)
Discussion started by: Shuinvy
2 Replies

2. Cybersecurity

differences between Shibboleth and Single Sign On

Could someone please explain to me the difference between Shibboleth and Single Sign On? How are they related? Thank you! (1 Reply)
Discussion started by: onlinelearner02
1 Replies

3. Solaris

Solaris Single Sign on options

We are looking for implementing solaris single sign on with AD in our environment which as few hundred Solaris hosts and couple of hundred solaris zones ..IS there any third party software for the same or we can do it by just making the solaris servers as AD clients ? Any help is appreciated. (1 Reply)
Discussion started by: fugitive
1 Replies

4. UNIX for Advanced & Expert Users

Problem: Single Sign On for linux

Hi gurus, I'd like to know your opions about Single Sign On (SSO) for linux (Debian). In my company, clients want to access to different services (FTP, HTTP, Mail, Web Applications ). I think about OpenLDAP and Proxy (Squid, Vulture) to resolve this problem but i'm not sure if they can. Are there... (0 Replies)
Discussion started by: thanhdat
0 Replies

5. UNIX for Dummies Questions & Answers

Urgent - Single User Mode -Unisys System V Release 4.0

Hello All, I have a Unisys 6000/65 machine running Unix System V Release 4.0.My problem is that we received an error that said "SPCS error occurred"and "vxfs:vx -ilisterr-inode 62585 mark bad /filesystem".The machine was stuck and I had to restart it.Now I cannot login from any workstation or... (2 Replies)
Discussion started by: liverpool
2 Replies

6. Shell Programming and Scripting

Read line with a single key press...

I would really like to have a script that will accept the key press from the user with out having to press the enter key afterwards. i.e. echo "Press Y to print \c" read YesNo At this point the user has to press the enter key to continue. Is there a way to accept the key press from the... (3 Replies)
Discussion started by: jagannatha
3 Replies
Login or Register to Ask a Question
CGI::Session::Driver::file(3)				User Contributed Perl Documentation			     CGI::Session::Driver::file(3)

NAME
CGI::Session::Driver::file - Default CGI::Session driver SYNOPSIS
$s = new CGI::Session(); $s = new CGI::Session("driver:file", $sid); $s = new CGI::Session("driver:file", $sid, {Directory=>'/tmp'}); DESCRIPTION
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. DRIVER ARGUMENTS 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. NOTES
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. LICENSING
For support and licensing see CGI::Session perl v5.16.3 2008-07-16 CGI::Session::Driver::file(3)