Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 452941 - Error on running chkrootkit -q (find: WARNING: Hard link count is wrong for /proc:)
Summary: Error on running chkrootkit -q (find: WARNING: Hard link count is wrong for /...
Alias: None
Product: Fedora
Classification: Fedora
Component: chkrootkit
Version: 8
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Michael Schwendt
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-26 05:06 UTC by Stefan Jensen
Modified: 2008-06-26 10:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-06-26 10:53:37 UTC

Attachments (Terms of Use)

Description Stefan Jensen 2008-06-26 05:06:58 UTC
Description of problem:

running "chkrootkit" without options runs fine.
running "chkrootkit -q" (eg: from cron or shell) produces errrors.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. install chkrootkit
2. run "chkrootkit -q" from shell  
Actual results:

error are printed out when running with "-q":

find: WARNING: Hard link count is wrong for /proc: this may be a bug in your
filesystem driver.  Automatically turning on find's -noleaf option.  Earlier
results may have failed to include directories that should have been searched.

Expected results:

no errors, as running without "-q" to suppress output.

Additional info:

"alias find='fin
d -noleaf'" in .bashrc doesn't help.

Comment 1 Michael Schwendt 2008-06-26 10:53:37 UTC
As the message says, it is a kernel bug. It is

  find /proc >/dev/null

which gives this warning, too, whenever it is reproducible.
It is not specific to chkrootkit.
-q means "quiet" and has nothing to do with this.

It is being worked on by the upstream kernel developers, I think.

Note You need to log in before you can comment on or make changes to this bug.