erik quanstrom wrote:
One usage scenario of walkfs is to implement find, du, walk, rdup and
the like. Another usage [scenario] of walkfs, with the -s option, is to add file
indexing to a
fileserver.
this seems more complicated than a straightforward
non-fileserver based implementation. why do you
need a fileserver for this?
- erik
- Every three months there need to be a discussion about 'find', right ;)
- walkfs can cache/reuse results from previous runs
- arbitrary filesystem indexing and lookup schemes can be implemented
without changing the frontend-interface. Consider mime-type or
keyword lookup
- no more hassle with space or other special characters in filenames
- inaccessible parts of the filesystem are just masked out, instead of
returning
errors.
- ...
frontend tools are simple straightforward rc-scripts, consider:
find:
get a new walker thread
write filter to ctl file
write path to root file
while !eof {
path = read data
do with path whatever has been specified
}
du -s:
get a new walker thread
write path to root file
write "mode=stat" to the ctl file
read data (and block until walk is done)
print count and size
Best Regards,
Jorge-León
