Over a year old, never addressed. Closing.
I think it eventually went away so probably fixed.
** Changed in: chkrootkit (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to chkrootkit in Ubuntu.
forgot to reset to new when I added my update.
** Changed in: chkrootkit (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to chkrootkit in Ubuntu.
https://bugs.launchpad.net/bugs/828437
Title:
Serge: at the moment, no. I can't manually reproduce it. However, I
left the machine sitting over night and came back this morning to find
that it was stuck yet again, this time, the egrep process was using
7.1GB of 8GB, but PS only showed 2 instances running...
I'm currently running tiger
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to chkrootkit in Ubuntu.
https://bugs.launchpad.net/bugs/828437
Title:
chkrootkit cron job went nuts, spawned 14 instances and consumed
nearly 90% of my ram
To manage notifications
This is a batch mode output from top, showing the egrep process
consuming 6.7GB of my RAM...
** Attachment added: top.log
https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+attachment/2287476/+files/top.log
--
You received this bug notification because you are a member of
this is a capture of ps axf before rebooting the system to make it
usable again. Notice the 14 instances of egrep spawned by chkrootkit.
** Attachment added: ps-axf.log
https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/828437/+attachment/2287477/+files/ps-axf.log
--
You received
Also, this might actually be an issue created by tiger, rather than
chkrootkit itself...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to chkrootkit in Ubuntu.
https://bugs.launchpad.net/bugs/828437
Title:
chkrootkit cron job went
Thanks for taking the time to submit this bug. It does seem from the
ps forest output that tiger is the initial problem.
Is this easily reproducible with tiger? If so, if you run chkrootkit
without tiger, does it work fine?
(If so, we know where to start looking and we should retarget the bug)
