[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: rapidly proliferating sess files in /tmp, eating inodes



On Sat, May 24, 2014 at 10:31 AM, Tony Baldwin <tony@tonybaldwin.info> wrote:
> On Sat, May 24, 2014 at 09:54:37AM +0900, Joel Rees wrote:
>> On Sat, May 24, 2014 at 8:29 AM, Tony Baldwin <tony@tonybaldwin.info> wrote:
>> > Yesterday I could not log into a site on a little server here in my office.
>> > I ssh-ed to the box, and found that the "disk is full" (thus could not write to disk).
>> > df -h showed nothing of the sort, but df -i showed that / was 100% full of inodes.
>> > I'v e since found that apache2 is writing files with names of a nature like
>> > sess_908H908NF90821089HGARBleddygo0KH3r3
>> > in /tmp at a rate of about 20 or 30 files/minute.
>> > [...]
>>
>> Does searching the web for "sess files" produce any meaningful results?
>>
>> https://www.google.com/search?q=sess+files
>
> You must have meant
> https://duckduckgo.com/?q=sess+files

Let's see what the ducking guys give me.

Hmm. Looks a bit different.

> And, nope, nothing useful.

I must say, unless the region the searches are being performed from
have specific significant effects, you didn't find anything I would
expect to be useful with your search.

The question of how evil google is/was/is becoming aside, the only
search site I find myself avoiding is bing. But I even go there
sometimes.

-- 
Joel Rees

Be careful where you see conspiracy.
Look first in your own heart.


Reply to: