This is a discussion on howto prevent updatedb from checking mounted fs? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> The problem is that when a remote fs is mounted updatedb runs eternaly even if the remote system is ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| |||
| serge_moscou wrote: > is there a way to indicate to updatedb not to check a fs? man updatedb > And what is prunefs? <http://www.die.net/doc/linux/man/man5/updatedb.conf.5.html> easily found with a two-second google search. really, a little googling never hurt anyone. -- Joost Kremers joostkremers@yahoo.com Selbst in die Unterwelt dringt durch Spalten Licht EN:SiS(9) |
| |||
| "serge_moscou" <serge_mtu@mtu-net.ru> wrote: > The problem is that when a remote fs is mounted updatedb runs eternaly > even if the remote system is down. That seems like a minor problem to me. The fact that you rely that hard on a server which often is down sounds like a bigger problem. > is there a way to indicate to updatedb not to check a fs? I have the following default /etc/updatedb.conf in Slackware 9.1: -8<------------------------------------- PRUNEFS="devpts NFS nfs afs proc smbfs autofs iso9660 udf" PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /net" export PRUNEFS export PRUNEPATHS -8<------------------------------------- So mounted file systmes like nfs and smbfs will not be searched. Did you alter your updatedb.conf or does updatedb.conf look different in other versions of Slackware? Is your remote mount something else than nfs or smbfs? But again, maybe you should do some rethinking about your network topology. You should only rely on servers that are reliable. Unreliable servers can be somewhat more useful with an automounter, but still reliable servers are to prefer. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc1(at)poolhem.se Examples of addresses which go to spammers: root@localhost postmaster@localhost |
| ||||
| thank you very much Indeed I should have more confidence in man pages and be less lazy:-)) :-) It's crystal clear "Henrik Carlqvist" <Henrik.Carlqvist@deadspam.com> ???????/???????? ? ???????? ?????????: news > "serge_moscou" <serge_mtu@mtu-net.ru> wrote: > >> The problem is that when a remote fs is mounted updatedb runs eternaly >> even if the remote system is down. > > That seems like a minor problem to me. The fact that you rely that hard on > a server which often is down sounds like a bigger problem. > >> is there a way to indicate to updatedb not to check a fs? > > I have the following default /etc/updatedb.conf in Slackware 9.1: > > -8<------------------------------------- > PRUNEFS="devpts NFS nfs afs proc smbfs autofs iso9660 udf" > PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /net" > export PRUNEFS > export PRUNEPATHS > -8<------------------------------------- > > So mounted file systmes like nfs and smbfs will not be searched. > > Did you alter your updatedb.conf or does updatedb.conf look different in > other versions of Slackware? Is your remote mount something else than nfs > or smbfs? > > But again, maybe you should do some rethinking about your network > topology. You should only rely on servers that are reliable. Unreliable > servers can be somewhat more useful with an automounter, but still > reliable servers are to prefer. > > regards Henrik > -- > The address in the header is only to prevent spam. My real address is: > hc1(at)poolhem.se Examples of addresses which go to spammers: > root@localhost postmaster@localhost > |