blocks|key|350340|text|使用cron和find删除超过给定阈值的文件。例如，删除至少一周未被访问过的文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350341|find+.session/+-atime+%2B7++-exec+rm+{}+\;|code-block|syntax|javascript|350342|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Use cron with find to delete files older than given threshold. 
For example to delete files that haven't been accessed for at least a week.

<pre><code>find .session/ -atime +7 -exec rm {} \;
</code></pre>

blocks|key|347717|text|Debian/Ubuntu使用/etc/cron.d/php5中定义的cronjob处理此问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|347718|#+/etc/cron.d/php5:+crontab+fragment+for+php5
#++This+purges+session+files+older+than+X,+where+X+is+defined+in+seconds
#++as+the+largest+value+of+session.gc_maxlifetime+from+all+your+php.ini
#++files,+or+24+minutes+if+not+defined.++See+/usr/lib/php5/maxlifetime

#+Look+for+and+purge+old+sessions+every+30+minutes
09,39+*+++++*+*+*+++++root+++[+-d+/var/lib/php5+]+&&+find+/var/lib/php5/+-type+f+-cmin+%2B$(/usr/lib/php5/maxlifetime)+-print0+%7C+xargs+-r+-0+rm|code-block|syntax|javascript|347719|maxlifetime脚本通过检查php.ini返回会话应该保持活动状态的分钟数，如下所示|347720|#!/bin/sh+-e

max=1440

for+ini+in+/etc/php5/*/php.ini;+do
++++++++cur=$(sed+-n+-e+'s/%5E[[:space:]]*session.gc_maxlifetime[[:space:]]*=[[:space:]]*$[0-9]\%2B$.*$/\1/p'+$ini+2>/dev/null+%7C%7C+true);
++++++++[+-z+"$cur"+]+&&+cur=0
++++++++[+"$cur"+-gt+"$max"+]+&&+max=$cur
done

echo+$(($max/60))

exit+0|347721|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Debian/Ubuntu handles this with a cronjob defined in /etc/cron.d/php5

<pre><code># /etc/cron.d/php5: crontab fragment for php5
# This purges session files older than X, where X is defined in seconds
# as the largest value of session.gc_maxlifetime from all your php.ini
# files, or 24 minutes if not defined. See /usr/lib/php5/maxlifetime

# Look for and purge old sessions every 30 minutes
09,39 * * * * root [ -d /var/lib/php5 ] &amp;&amp; find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm
</code></pre>

The maxlifetime script simply returns the number of minutes a session should be kept alive by checking php.ini, it looks like this

<pre><code>#!/bin/sh -e

max=1440

for ini in /etc/php5/*/php.ini; do
 cur=$(sed -n -e 's/^[[:space:]]*session.gc_maxlifetime[[:space:]]*=[[:space:]]*$[0-9]\+$.*$/\1/p' $ini 2&gt;/dev/null || true);
 [ -z "$cur" ] &amp;&amp; cur=0
 [ "$cur" -gt "$max" ] &amp;&amp; max=$cur
done

echo $(($max/60))

exit 0
</code></pre>

blocks|key|346780|text|要正确处理会话，请看一下http://php.net/manual/en/session.configuration.php。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|346781|在那里你可以找到这些变量：|346782|346783|session.gc_probability|unordered-list-item|346784|session.gc_divisor|346785|session.gc_maxlifetime|346786|346787|它们控制垃圾收集器(GC)对每个页面请求运行的概率。|346788|您可以在脚本或.htaccess文件的开头使用ini_set()设置它们，这样您就可以在某种程度上确定它们将在某个时候被删除。|346789|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/session.configuration.php|1|http://php.net/manual/en/function.ini-set.php^0|C|1E|0|0|0|0|0|0|0|0|0|N|9|1|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|17|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|18|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|19|8|@]|9|@]|C|$]]|$1|L|3|M|5|I|7|1A|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|S|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]]]

To handle session properly, take a look at <a href="http://php.net/manual/en/session.configuration.php" rel="noreferrer">http://php.net/manual/en/session.configuration.php</a>.

There you'll find these variables:

<ul>
<li>session.gc_probability</li>
<li>session.gc_divisor</li>
<li>session.gc_maxlifetime</li>
</ul>

These control the garbage collector (GC) probability of running with each page request.

You could set those with <a href="http://php.net/manual/en/function.ini-set.php" rel="noreferrer">ini_set()</a> at the beginning of your script or .htaccess file so you get certainty to some extent they will get deleted sometime.

blocks|key|346796|text|我最好的猜测是，您在共享服务器上，会话文件与所有用户混合在一起，因此您不能也不应该删除它们。如果您担心可伸缩性和/或您的用户会话隐私，您可以做的是将会话移动到数据库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|346797|开始将Cookie写入数据库，当时间到期时，要在多个服务器上扩展您的应用程序还有很长的路要走。|346798|除此之外，我不会太担心145.000个文件。|346799|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

My best guess would be that you are on a shared server and the session files are mixed along all users so you can't, nor you should, delete them. What you can do, if you are worried about scaling and/or your users session privacy, is to move sessions to the database.

Start writing that Cookie to the database and you've got a long way towards scaling you app across multiple servers when time is due.

Apart from that I would not worry much with the 145.000 files.

blocks|key|350385|text|您可以创建脚本/etc/cron.hourly/php并将其放入：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|350386|#!/bin/bash

max=24
tmpdir=/tmp

nice+find+${tmpdir}+-type+f+-name+'sess_*'+-mmin+%2B${max}+-delete|code-block|syntax|javascript|350387|然后将脚本设为可执行文件(chmod+%2Bx)。|350388|现在每小时将删除所有在24分钟前修改过数据的会话文件。|350389|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You can create script /etc/cron.hourly/php and put there:

<pre><code>#!/bin/bash

max=24
tmpdir=/tmp

nice find ${tmpdir} -type f -name 'sess_*' -mmin +${max} -delete
</code></pre>

Then make the script executable (chmod +x). 

Now every hour will be deleted all session files with data modified more than 24 minutes ago.

blocks|key|3336674|text|如果有人想要使用cronjob执行此操作，请记住这一点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3336675|find+.session/+-atime+%2B7++-exec+rm+{}+\;|code-block|syntax|javascript|3336676|当有很多文件时，速度非常慢。|3336677|请考虑使用下面的代码：|3336678|find+.session/+-atime+%2B7+%7C+xargs+-r+rm|3336679|如果文件名中有空格，请使用以下命令：|3336680|find+.session/+-atime+%2B7+-print0+%7C+xargs+-0+-r+rm|3336681|xargs将用要删除的文件填充命令行，然后运行比-exec+rm+{}+\;少得多的rm命令，后者将为每个文件调用rm命令。|offset|length|style|CODE|3336682|这只是我的两点意见|3336683|entityMap^0|0|0|0|0|0|0|0|0|5|O|E|16|2|1L|2|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|17|8|@$S|18|T|19|U|V]|$S|1A|T|1B|U|V]|$S|1C|T|1D|U|V]|$S|1E|T|1F|U|V]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|Z|$]]

In case someone want's to do this with a cronjob, please keep in mind that this:

<pre><code>find .session/ -atime +7 -exec rm {} \;
</code></pre>

is really slow, when having a lot of files.

Consider using this instead:

<pre><code>find .session/ -atime +7 | xargs -r rm
</code></pre>

In Case you have spaces in you file names use this:

<pre><code>find .session/ -atime +7 -print0 | xargs -0 -r rm
</code></pre>

<code>xargs</code> will fill up the commandline with files to be deleted, then run the <code>rm</code> command a lot lesser than <code>-exec rm {} \;</code>, which will call the <code>rm</code> command for each file.

Just my two cents

blocks|key|346912|text|#+Every+30+minutes,+not+on+the+hour 
#+Grabs+maxlifetime+directly+from+\`php+-i\` 
#+doesn't+care+if+/var/lib/php5+exists,+errs+go+to+/dev/null 

09,39+*+*+*+*+++find+/var/lib/php5/+-type+f+-cmin+%2B$(echo+"\`php+-i%7Cgrep+-i+session.gc_maxlifetime%7Ccut+-d'+'+-f3\`+/+60"+%7C+bc)+-exec+rm+-f+{}+\\;+>/dev/null+2>&1|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|346913|分解:仅文件:php5//+-type+f|unstyled|offset|length|style|BOLD|346914|时间早于分钟：-cmin|346915|获取php设置：$(echo+"`php+-i%7Cgrep+-i+session.gc_maxlifetime|346916|计算一下：%7Ccut+-d‘’-f3`+/+60“%7C+bc)|346917|RM匹配文件：-exec+rm+-f+{}+\;|346918|entityMap^0|0|C|9|0|7|5|0|8|1A|0|5|O|0|7|H|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|V|8|@$G|W|H|X|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@$G|Z|H|10|I|J]]|9|@]|A|$]]|$1|M|3|N|5|F|7|11|8|@$G|12|H|13|I|J]]|9|@]|A|$]]|$1|O|3|P|5|F|7|14|8|@$G|15|H|16|I|J]]|9|@]|A|$]]|$1|Q|3|R|5|F|7|17|8|@$G|18|H|19|I|J]]|9|@]|A|$]]|$1|S|3|-4|5|F|7|1A|8|@]|9|@]|A|$]]]|T|$]]

<pre><code># Every 30 minutes, not on the hour&lt;br&gt;
# Grabs maxlifetime directly from \`php -i\`&lt;br&gt;
# doesn't care if /var/lib/php5 exists, errs go to /dev/null&lt;br&gt;

09,39 * * * * find /var/lib/php5/ -type f -cmin +$(echo "\`php -i|grep -i session.gc_maxlifetime|cut -d' ' -f3\` / 60" | bc) -exec rm -f {} \\; &gt;/dev/null 2&gt;&amp;1
</code></pre>

The Breakdown:
Only files: find /var/lib/php5/ -type f 
Older than minutes: -cmin 
Get php settings: $(echo "`php -i|grep -i session.gc_maxlifetime 
Do the math: |cut -d' ' -f3` / 60" | bc) 
RM matching files: -exec rm -f {} \;

blocks|key|3336755|text|使用下面的cron：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3336756|39+20+++++*+*+*+++++root+++[+-x+/usr/lib/php5/maxlifetime+]+&&+[+-d+/var/lib/php5+]+&&+find+/var/lib/php5/+-depth+-mindepth+1+-maxdepth+1+-type+f+-cmin+%2B$(/usr/lib/php5/maxlifetime)+-print0+%7C+xargs+-r+-0+rm|code-block|syntax|javascript|3336757|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Use below cron:

<pre><code>39 20 * * * root [ -x /usr/lib/php5/maxlifetime ] &amp;&amp; [ -d /var/lib/php5 ] &amp;&amp; find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm
</code></pre>

blocks|key|345532|text|cd转到会话目录，然后：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|345533|1)查看超过40分钟的会话：find+.+-amin+%2B40+-exec+stat+-c+"%25n+%25y"+{}+\;|offset|length|style|CODE|345534|2)删除超过40分钟的会话：find+.+-amin+%2B40++-exec+rm+{}+\;|345535|entityMap^0|0|E|18|0|E|W|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

cd to sessions directory and then:

1) View sessions older than 40 min:
 <code>find . -amin +40 -exec stat -c "%n %y" {} \;</code>

2) Remove sessions older than 40 min: 
<code>find . -amin +40 -exec rm {} \;</code>

On my website I use PHP sessions. Session information is stored in files in my ./session path. After a few months I discovered that these session files are never deleted, by now there are 145.000 of them in this directory. 

How should these be cleaned up? Do I have to do it programmatically, or is ther a setting I can use somewhere that would have this cleanup happen automatically?

EDIT forgot to mention: This site runs at a provider, so I don't have access to a command line. I do have ftp-access, but the session files belong to another user (the one the webserver proces runs I guess) From the first answers I got I think it's not just a setting on the server or PHP, so I guess I'll have to implement something for it in PHP, and call that periodically from a browser (maybe from a cron job running on my own machine at home)

cleanup php session files

数据库

服务器

Ubuntu

Debian

在我的网站上，我使用PHP会话。会话信息存储在my./ Session路径下的文件中。几个月后，我发现这些会话文件从来没有被删除过，到目前为止，在这个目录中有145.000个。这些应该如何清理呢？我是否必须通过编程来完成这项工作，或者有没有一种设置可以让此清理工作自动进行？EDIT忘了提一下:这个站点是在提供商那里运行...

问清理php会话文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问清理php会话文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问清理php会话文件
EN