This morning there were no "find" jobs running. It appears that adding
/proc to prunepaths
did work.
/usr/bin/updatedb --localpaths="/ /c" --prunepaths="/a/proc"
Arun
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Arun Biyani on 7/10/2006 5:23 PM:
I hav
I am running it now with the command line -
/usr/bin/updatedb --localpaths="/ /c" --prunepaths="/a/proc"
Arun
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Arun Biyani on 7/10/2006 5:23 PM:
I have been running "updatedb" via a cron job for almost 6 month
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Arun Biyani on 7/10/2006 5:23 PM:
> I have been running "updatedb" via a cron job for almost 6 months now.
> It is started
> at 11PM & is usually done in an hour. Recently, I have been noticing
> that there is a
> "find" job still running
I have been running "updatedb" via a cron job for almost 6 months now.
It is started
at 11PM & is usually done in an hour. Recently, I have been noticing
that there is a
"find" job still running when I get in, in the morning. My crontab has -
# run updatedb daily
5 22 * * * /usr/bin/updatedb --
4 matches
Mail list logo