Package: chkrootkit
Version: 0.50-2
Severity: important

Hi, chkrootkit hangs on checking lkm, and the system load increases by ~1.0 
until I kill it.

$ strace chkrootkit
[..]
wait4(-1, Checking `lkm'...                                           
[{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 7071
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=7071, si_uid=0, 
si_status=0, si_utime=0, si_stime=0} ---
rt_sigreturn()                          = 7071
pipe([3, 4])                            = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x7f13be4189d0) = 7072
close(4)                                = 0
read(3, "1\n", 128)                     = 2
read(3, "", 128)                        = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=7072, si_uid=0, 
si_status=0, si_utime=0, si_stime=0} ---
rt_sigreturn()                          = 0
close(3)                                = 0
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 7072
pipe([3, 4])                            = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x7f13be4189d0) = 7079
close(4)                                = 0
read(3, ^CProcess 31984 detached
 <detached ...>

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages chkrootkit depends on:
ii  binutils               2.24.90.20141023-1
ii  debconf [debconf-2.0]  1.5.53
ii  libc6                  2.19-13
ii  net-tools              1.60-26+b1
ii  procps                 2:3.3.9-8

chkrootkit recommends no packages.

chkrootkit suggests no packages.

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to