Bug 2728 - updatedb (bdflush)
Summary: updatedb (bdflush)
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: findutils
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-05-11 07:27 UTC by stef.pillaert
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 1999-06-01 19:24:35 UTC
Embargoed:


Attachments (Terms of Use)

Description stef.pillaert 1999-05-11 07:27:34 UTC
Don't know if this is a bug, but locate acts strange now and
then, so...

I notice that updatedb keeps on running (forever?)
"ps aux" shows:

updatedb(bdflush)

Should there be something excluded in slocate? Or is this
behaviour normal?

Thanks,

Stef.

Comment 1 Bill Nottingham 1999-05-11 14:35:59 UTC
that's update (bdflush), which is the kernel's cache
flushing-daemon. It doesn't have anything to do with
slocate.

Comment 2 stef.pillaert 1999-05-12 07:10:59 UTC
OOPS!! Very sorry!
But the reason I got confused was: running "updatedb" (and not
slocate, sorry) hangs. (and I thought it was launched at startup, and
confused it with update)

Should I exclude something from updatedb?
Thanks.

Stef.

Comment 3 Bill Nottingham 1999-05-13 15:04:59 UTC
If you do 'strace -o output updatedb', and then look at
the output file when it hangs, where is it hanging?

Comment 4 Jeff Johnson 1999-05-15 22:33:59 UTC
*** This bug has been marked as a duplicate of 2682 ***

Comment 5 stef.pillaert 1999-05-17 08:32:59 UTC
Well, it seems to hang when doing "chdir(".automount")". Do you want
me to give you the details given by strace?
Stef.

Comment 6 Jeff Johnson 1999-06-01 19:02:59 UTC
I've replace updatedb in slocate-1.6-1 to more perfectly imitate
the behavior of the findutils updatedb. This means that certain
directories and NFS or smb mount points will not be searched while
building the slocate database.


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