Hi Craig,
On Mon, Jul 18, 2011 at 00:25, Craig Small csm...@debian.org wrote:
On Sun, Jul 17, 2011 at 11:53:37PM +0200, Luka Frelih wrote:
what i can confirm from investigation is that version 22.14-1 of
fuser uses many times more resources - cpu and ram - than the stable
version. why this
On Wed, Feb 08, 2012 at 08:49:59PM +0100, Ondřej Surý wrote:
On Mon, Jul 18, 2011 at 00:25, Craig Small csm...@debian.org wrote:
I'm probably going to revert the change and make it an option.
Did you ever get to it? Should I fill a minor/wishlist bug against psmisc
to make you not forget?
Hi,
since the scanning of the full /proc directory on every file in the
/var/lib/php5 is very ineffective, I am probably going to remove the
fuser call and replace it with something like this (rewritten to C for
speed and less forks and bashisms removed):
MAXTIME=$(/usr/lib/php5/maxlifetime)
hello!
craig, good idea to make the new potentially buggy behaviour an opt-in
switch.
ondřej, this command runs in acceptable time, around 10 seconds
(similar to performance of find with stable fuser). but it does not
actually delete anything, i tried it from cron as well as bash. seems
Hi,
have you tested it yourself or have you just made conclusion on a blog post?
howl:/# dpkg -l psmisc
ii psmisc 22.14-1
utilities that use the proc
file system
howl:/# fuser /bin/bash; echo $?
/bin/bash:
hello!
thanks for your interest! my characterization of the bug in fuser is
wrong, you are right.
ccing also craig, the maintainer of psmisc
but i have experienced many times this week all the daemons on our
server being killed due to OOM (i guess) because of the php5 cron job.
this leaves
On Sun, Jul 17, 2011 at 11:53:37PM +0200, Luka Frelih wrote:
what i can confirm from investigation is that version 22.14-1 of
fuser uses many times more resources - cpu and ram - than the stable
version. why this is, i don't know. but used in the find for
That would be the forking that goes on
7 matches
Mail list logo
