mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-15 16:38:54 +00:00
Minimum gc_maxlifetime is used (bug #34588)
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@198355 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
90f74ac6c5
commit
85bd327a52
1 changed files with 11 additions and 2 deletions
|
@ -1,5 +1,5 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.35 $ -->
|
||||
<!-- $Revision: 1.36 $ -->
|
||||
<section id="session.configuration">
|
||||
&reftitle.runtime;
|
||||
&extension.runtime;
|
||||
|
@ -344,12 +344,21 @@
|
|||
of seconds after which data will be seen as 'garbage' and
|
||||
cleaned up.
|
||||
</simpara>
|
||||
<note>
|
||||
<para>
|
||||
If different scripts have different values of
|
||||
<literal>session.gc_maxlifetime</literal> but shares the same place for
|
||||
storing the session data then the script with the minimum value will be
|
||||
cleaning the data. In this case, use this directive together with <link
|
||||
linkend="ini.session.save-path">session.save_path</link>.
|
||||
</para>
|
||||
</note>
|
||||
<note>
|
||||
<simpara>If you are using the default file-based session handler, your
|
||||
filesystem must keep track of access times (atime). Windows FAT does
|
||||
not so you will have to come up with another way to handle garbage
|
||||
collecting your session if you are stuck with a FAT filesystem or any
|
||||
other fs where atime tracking is not available.
|
||||
other filesystem where atime tracking is not available.
|
||||
Since PHP 4.2.3 it has used mtime (modified date) instead of atime. So, you
|
||||
won't have problems with filesystems where atime tracking is not available.
|
||||
</simpara>
|
||||
|
|
Loading…
Reference in a new issue