Results 1 to 4 of 4

Thread: looking for realtime alternative to locate (updatedb)

  1. #1
    google01103 NNTP User

    Default looking for realtime alternative to locate (updatedb)

    Looking for a real time alternative to the updatedb function of locate, similar to rlocate which I've not been able to run on the last couple of releases of Suse (and yes I tried removing appArmor).

    I've looked at tracker, beagle and recoll and they don't seem to be able to do this, though I would be happy to be corrected.

    thanks,

    --
    Suse 11.0 x64, Kde 4.1beta (factory repo), Opera 9.x weekly

  2. #2
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: looking for realtime alternative to locate (updatedb)

    > I've looked at ... beagle ... don't seem to be able to do this,
    > though I would be happy to be corrected.


    beagle's configuration dialog lets you add any (all?) folders you
    want indexed..

    however, most folks find the performance hit that dog makes when it
    is only indexing /home to be bad enough that they send the hound out
    of the house..

    but, the fact is that once it has been around and sniffed everything
    it is not so terribly obtrusive after the initial BIG HIT is over..

    you might wanna give it a try *IF* you can just turn your machine on
    and NOT expect to do anything with it for an hour or *more* (if your
    /home is already large)...i have NO idea how long it would take to
    index an entire system (overnight maybe)...well you don't actually
    need to index /proc, /dev, /mnt, /media or /????

    AND, if you do like many and shutdown the machine at night (or more
    often) then you must be warned that EVERY time you boot up you have
    to expect the dog to steal LOTS of cycles to (i guess) make sure it
    knows what is where, and lift a leg and 'mark it'....or something...

    personally, i use locate....the once daily db update is usually often
    enough, for me...i know your needs might well be different..

    here, if i really have to i just to a command line and
    sudo updatedb

    or, if _you_ have lots needed updatedb options (or just want to make
    it easy) you can always make a little script and give it a button on
    your task bar/desktop/etc..

    i just timed an update on my (admittedly not so huge drive) and it
    took about 4 minutes...which is far cry from the time hit you will
    take with beagle..

    --
    DenverD (Linux Counter 282315) via NNTP, Thunderbird 2.0.0.14, KDE
    3.5.7, SUSE Linux 10.3, 2.6.22.18-0.2-default #1 SMP i686 athlon

  3. #3
    google01103 NNTP User

    Default Re: looking for realtime alternative to locate (updatedb)

    DenverD wrote:

    >> I've looked at ... beagle ... don't seem to be able to do this,
    >> though I would be happy to be corrected.

    >
    > beagle's configuration dialog lets you add any (all?) folders you
    > want indexed..
    >
    > however, most folks find the performance hit that dog makes when it
    > is only indexing /home to be bad enough that they send the hound out
    > of the house..
    >
    > but, the fact is that once it has been around and sniffed everything
    > it is not so terribly obtrusive after the initial BIG HIT is over..
    >
    > you might wanna give it a try *IF* you can just turn your machine on
    > and NOT expect to do anything with it for an hour or *more* (if your
    > /home is already large)...i have NO idea how long it would take to
    > index an entire system (overnight maybe)...well you don't actually
    > need to index /proc, /dev, /mnt, /media or /????
    >
    > AND, if you do like many and shutdown the machine at night (or more
    > often) then you must be warned that EVERY time you boot up you have
    > to expect the dog to steal LOTS of cycles to (i guess) make sure it
    > knows what is where, and lift a leg and 'mark it'....or something...
    >
    > personally, i use locate....the once daily db update is usually often
    > enough, for me...i know your needs might well be different..
    >
    > here, if i really have to i just to a command line and
    > sudo updatedb
    >
    > or, if _you_ have lots needed updatedb options (or just want to make
    > it easy) you can always make a little script and give it a button on
    > your task bar/desktop/etc..
    >
    > i just timed an update on my (admittedly not so huge drive) and it
    > took about 4 minutes...which is far cry from the time hit you will
    > take with beagle..
    >
    > --
    > DenverD (Linux Counter 282315) via NNTP, Thunderbird 2.0.0.14, KDE
    > 3.5.7, SUSE Linux 10.3, 2.6.22.18-0.2-default #1 SMP i686 athlon

    my understanding is that even if I used Beagle it would index all those files unlike updatedb which just creates a db of what files exist.

    What I seem to dislike most about updatedb (other then it's not realtime) is that it seems to not release ram after it's run (at least according to my system monitor applet)
    --
    Suse 11.0 x64, Kde 4.1beta (factory repo), Opera 9.x weekly

  4. #4
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: looking for realtime alternative to locate (updatedb)


    > my understanding is that even if I used Beagle it would index all
    > those files unlike updatedb which just creates a db of what files
    > exist.


    to me, "beagle indexing" _is_ building/updating an database


    > What I seem to dislike most about updatedb (other then it's not
    > realtime)


    as mentioned it is 'realtime' once a day, or about 4 minutes after
    doing a manual update..


    > is that it seems to not release ram after it's run (at
    > least according to my system monitor applet)


    my understanding is that initially Linux will 'hold on to' data in
    memory just in case it needs the data again...soon...and, then the
    next time an app needs memory it will allocate the OLDEST being
    held....so, all the other held memory that is older (from other apps
    closed before updatedb) will be used first..

    i've not shut my machine down since i ran updatedb this morning, and
    my KDE System Guard Process Table shows no memory allocated to
    upgradedb (neither does top nor atop)...however, i'm not looking at
    yours....does updatedb close cleanly?

    and, i also wonder why you have trouble with rlocate....is it a bug?

    --
    DenverD (Linux Counter 282315) via NNTP, Thunderbird 2.0.0.14, KDE
    3.5.7, SUSE Linux 10.3, 2.6.22.18-0.2-default #1 SMP i686 athlon

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •