On 28 May 2005 12:27:17 +0100, Jeremy Laine wrote: > > On 2 servers already I have noticed that /tmp progressively fills up with > temporary Arch directories belonging to www-data when using archzoom. I > am not sure what is causing this behaviour, as I am not able to > "manually" (i.e by browsing archzoom myself) reproduce the problem. > The problem possibly occurs as a result of search bots indexing the > archzoom.
I am aware of this problem. However, I don't know the exact reason yet. One possibility is Apache kills archzoom (hard ulimit exceeds or maybe a client connection is closed). It was my plan to unconditionally remove old $tmp_dir/,,* dirs, but I would like to know the reason first. Please provide stats, like "9 ,,arch-cset-* dirs this week occupying 60Kb, 15 ,,arch-tree-* dirs occupying 200Kb". Also it would be nice it you note the time of several such dirs and find the corresponding logs/access_log lines, maybe there is some pattern here. And please send me archzoom urls (note, "0.5.0 (devel)" that Google returns means any 0.4.2+ snapshot.) So far users reported mostly empty ,,arch-cset-*. For now, you may setup hourly cronjob: rm -rf `find /tmp -mtime +0 -name ',,*' -maxdepth 1` Regards, Mikhael. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
