Re: locate question

[Greg Wooledge]

On Wed, Nov 08, 2023 at 05:16:26PM +0100, to...@tuxteam.de wrote:
> On Wed, Nov 08, 2023 at 11:45:30AM -0400, Roy J. Tellason, Sr. wrote:
> > On Tuesday 07 November 2023 11:32:21 am gene heskett wrote:
> > > so locate isn't working as I think it should.
> > > try find but it finds the whole my whole local net:
> > > gene@coyote:~$ find .scad .  |wc -l
> > > find: ‘.scad’: No such file or directory
> > 
> > Try putting a * before the period in that find command?
> 
> No, it is more than that. [...]

> Putting a * in front of it would get expanded *by the
> shell* (not by find), as was discussed elsewhere in this
> thread. Find would see the expanded result, so, if e.g.
> you have foo.scad, bar.scad and baz.scad in your current
> dir, the command actually run would be
> 
>   find foo.scad bar.scad baz.scad

Also note that there are *two* periods in Gene's original find command.
He's asking find to look for stuff, beginning in ".scad" and then also
beginning in ".".

If you changed it to

find *.scad .

then it would ask find to look for stuff beginning in "foo.scad" and
also beginning in "bar.scad" and also beginning in ".".

Changing it to

find '*.scad' .

would ask find to look for stuff beginning in "*.scad" (a literal
asterisk character) and then also beginning in ".".  That's still not
what's wanted.

What's wanted was already posted earlier, but just for redundancy:

find . -iname '*.scad'

is probably the best answer.  You can use -name instead of -iname if
you want the matching to be case sensitive.

Re: locate question

[tomas]

On Wed, Nov 08, 2023 at 11:45:30AM -0400, Roy J. Tellason, Sr. wrote:
> On Tuesday 07 November 2023 11:32:21 am gene heskett wrote:
> > so locate isn't working as I think it should.
> > try find but it finds the whole my whole local net:
> > gene@coyote:~$ find .scad .  |wc -l
> > find: ‘.scad’: No such file or directory
> 
> Try putting a * before the period in that find command?

No, it is more than that. The non-option arguments to find
are the starting points. So "find .scad" would look for
something (hopefully a directory, but in a pinch, a file
would do, see below) and find everything in there which
fulfills the search criteria.

Since those are empty, you would get a listing of .scad
and everything below it. If there's no .scad, the result
is empty.

Putting a * in front of it would get expanded *by the
shell* (not by find), as was discussed elsewhere in this
thread. Find would see the expanded result, so, if e.g.
you have foo.scad, bar.scad and baz.scad in your current
dir, the command actually run would be

  find foo.scad bar.scad baz.scad

which would, if those are plain files, just list those
three (something you can get far cheaper with ls).

Cheers
-- 
tomás


signature.asc
Description: PGP signature

Re: locate question

[Roy J. Tellason, Sr.]

On Tuesday 07 November 2023 11:32:21 am gene heskett wrote:
> so locate isn't working as I think it should.
> try find but it finds the whole my whole local net:
> gene@coyote:~$ find .scad .  |wc -l
> find: ‘.scad’: No such file or directory

Try putting a * before the period in that find command?

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: locate question

[Jörg-Volker Peetz]

If you just want to see files in /home/gene try

  locate -r 'home/gene/.*\.scad'

In that way, regex syntax can be used to narrow down the search.

Regards,
Jörg.

Re: locate question

[gene heskett]

On 11/7/23 14:38, to...@tuxteam.de wrote:

On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote:

Greetings all;


[...]


gene@coyote:~$ locate *.scad
/home/gene/vac_ctrl_box.scad
/home/gene/xhome_cable.scad


Markus and The Wanderer were spot on.

As a reminder to all: this "naked" *.scad gets already expanded
by the shell (try "echo *.scad"), so what locate gets to see is
an already expanded list of all files ending in .scad in whatever
directory you happen to be, most probably:

   locate vac_ctrl_box.scad xhome_cable.scad

... because these are most probably the only two files matching
that glob pattern living in your home directory (where you happen
to be, if your prompt ain't lying to us).

Shell is handy, but shell is nasty at times.


And its regex needs housebroke much of the time. ;o)>


Cheers


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: locate question

[gene heskett]

On 11/7/23 14:24, mick.crane wrote:

On 2023-11-07 16:32, gene heskett wrote:

Greetings all;
I dunno if I've forgot how to use it, or it broken by the same bug
that killing me with the lagging access to my home raid10.

Fact: there are probably over 100 files in my /home/gene directory and
all its subs with assorted names ending in ".scad", made by OpenSCAD
Fact: I just ran "sudo updatedb" and generated a new date just now,
/var/cache/locate/locatedb.n
so that s/b uptodate.
Al of those files should be spit out by:
"locate *.scad" issued from an xfce terminal
but I get:
gene@coyote:~$ locate *.scad
/home/gene/vac_ctrl_box.scad
/home/gene/xhome_cable.scad


I dunno.
You can make separate local databases for locate.
maybe try that.
mick

That sounds helpful as I generally am not interested in random hits from 
the rest of the system. I'll read the manpage again. Thanks mick

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: locate question

[gene heskett]

On 11/7/23 11:52, Markus Schönhaber wrote:

Am 07.11.23 um 17:32 schrieb gene heskett:


Greetings all;
I dunno if I've forgot how to use it, or it broken by the same bug that
killing me with the lagging access to my home raid10.

Fact: there are probably over 100 files in my /home/gene directory and
all its subs with assorted names ending in ".scad", made by OpenSCAD
Fact: I just ran "sudo updatedb" and generated a new date just now,
/var/cache/locate/locatedb.n
so that s/b uptodate.
Al of those files should be spit out by:
"locate *.scad" issued from an xfce terminal
but I get:
gene@coyote:~$ locate *.scad


Since you're not escaping the '*' you (i. e. the shell) implicitly did:

gene@coyote:~$ locate vac_ctrl_box.scad xhome_cable.scad

instead, try

gene@coyote:~$ locate .scad


/home/gene/vac_ctrl_box.scad
/home/gene/xhome_cable.scad

Acc an ls -R|wc -l  there are
433179
files in my /home/gene directory

so locate isn't working as I think it should.
try find but it finds the whole my whole local net:


No, it searches starting at ".scad" and ".". The former doesn't exist
and the latter is your home directory (because that is the $CWD when you
issued the command) which find recursively searches for everything,
since you didn't specify what to search for.


gene@coyote:~$ find .scad .  |wc -l
find: ‘.scad’: No such file or directory
1176532



What am I doing wrong?


Try

gene@coyote:~$ find . -name '*.scad'


And that works, thanks all.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis

Re: locate question

[Greg Wooledge]

On Tue, Nov 07, 2023 at 08:38:51PM +0100, to...@tuxteam.de wrote:
> On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote:
> > gene@coyote:~$ locate *.scad
> > /home/gene/vac_ctrl_box.scad
> > /home/gene/xhome_cable.scad
> 
> Markus and The Wanderer were spot on.
> 
> As a reminder to all: this "naked" *.scad gets already expanded
> by the shell (try "echo *.scad"), so what locate gets to see is
> an already expanded list of all files ending in .scad in whatever
> directory you happen to be, most probably:
> 
>   locate vac_ctrl_box.scad xhome_cable.scad
> 
> ... because these are most probably the only two files matching
> that glob pattern living in your home directory (where you happen
> to be, if your prompt ain't lying to us).

And THAT is why we like to see the shell prompt along with the
command and its output.  It tells us (or gives us strong hints about)
the current working directory and whether the command is being executed
as a normal user or a UID=0 user.

Re: locate question

[tomas]

On Tue, Nov 07, 2023 at 11:32:21AM -0500, gene heskett wrote:
> Greetings all;

[...]

> gene@coyote:~$ locate *.scad
> /home/gene/vac_ctrl_box.scad
> /home/gene/xhome_cable.scad

Markus and The Wanderer were spot on.

As a reminder to all: this "naked" *.scad gets already expanded
by the shell (try "echo *.scad"), so what locate gets to see is
an already expanded list of all files ending in .scad in whatever
directory you happen to be, most probably:

  locate vac_ctrl_box.scad xhome_cable.scad

... because these are most probably the only two files matching
that glob pattern living in your home directory (where you happen
to be, if your prompt ain't lying to us).

Shell is handy, but shell is nasty at times.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: locate question

[mick.crane]

On 2023-11-07 16:32, gene heskett wrote:

Greetings all;
I dunno if I've forgot how to use it, or it broken by the same bug
that killing me with the lagging access to my home raid10.

Fact: there are probably over 100 files in my /home/gene directory and
all its subs with assorted names ending in ".scad", made by OpenSCAD
Fact: I just ran "sudo updatedb" and generated a new date just now,
/var/cache/locate/locatedb.n
so that s/b uptodate.
Al of those files should be spit out by:
"locate *.scad" issued from an xfce terminal
but I get:
gene@coyote:~$ locate *.scad
/home/gene/vac_ctrl_box.scad
/home/gene/xhome_cable.scad


I dunno.
You can make separate local databases for locate.
maybe try that.
mick

Re: locate question

[The Wanderer]

On 2023-11-07 at 11:32, gene heskett wrote:

> Greetings all;
> I dunno if I've forgot how to use it, or it broken by the same bug that 
> killing me with the lagging access to my home raid10.
> 
> Fact: there are probably over 100 files in my /home/gene directory and 
> all its subs with assorted names ending in ".scad", made by OpenSCAD
> Fact: I just ran "sudo updatedb" and generated a new date just now,
> /var/cache/locate/locatedb.n
> so that s/b uptodate.
> Al of those files should be spit out by:
> "locate *.scad" issued from an xfce terminal
> but I get:
> gene@coyote:~$ locate *.scad
> /home/gene/vac_ctrl_box.scad
> /home/gene/xhome_cable.scad

Try instead:

$ locate '*.scad'

That should prevent the shell from expanding the wildcard before running
the command.

> Acc an ls -R|wc -l  there are
> 433179
> files in my /home/gene directory
> 
> so locate isn't working as I think it should.
> try find but it finds the whole my whole local net:
> gene@coyote:~$ find .scad .  |wc -l
> find: ‘.scad’: No such file or directory
> 1176532

Try

$ find . -name '*.scad'

> What am I doing wrong?

For locate, you're not quoting the arguments properly.

For find, you're also putting the arguments in the wrong order.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: locate question

[Markus Schönhaber]

Am 07.11.23 um 17:32 schrieb gene heskett:

> Greetings all;
> I dunno if I've forgot how to use it, or it broken by the same bug that
> killing me with the lagging access to my home raid10.
> 
> Fact: there are probably over 100 files in my /home/gene directory and
> all its subs with assorted names ending in ".scad", made by OpenSCAD
> Fact: I just ran "sudo updatedb" and generated a new date just now,
> /var/cache/locate/locatedb.n
> so that s/b uptodate.
> Al of those files should be spit out by:
> "locate *.scad" issued from an xfce terminal
> but I get:
> gene@coyote:~$ locate *.scad

Since you're not escaping the '*' you (i. e. the shell) implicitly did:

gene@coyote:~$ locate vac_ctrl_box.scad xhome_cable.scad

instead, try

gene@coyote:~$ locate .scad

> /home/gene/vac_ctrl_box.scad
> /home/gene/xhome_cable.scad
> 
> Acc an ls -R|wc -l  there are
> 433179
> files in my /home/gene directory
> 
> so locate isn't working as I think it should.
> try find but it finds the whole my whole local net:

No, it searches starting at ".scad" and ".". The former doesn't exist
and the latter is your home directory (because that is the $CWD when you
issued the command) which find recursively searches for everything,
since you didn't specify what to search for.

> gene@coyote:~$ find .scad .  |wc -l
> find: ‘.scad’: No such file or directory
> 1176532
>>
> What am I doing wrong?

Try

gene@coyote:~$ find . -name '*.scad'

-- 
Regards
  mks

Re: locate question

[Pocket]

On 11/7/23 11:32, gene heskett wrote:

Greetings all;
I dunno if I've forgot how to use it, or it broken by the same bug 
that killing me with the lagging access to my home raid10.


Fact: there are probably over 100 files in my /home/gene directory and 
all its subs with assorted names ending in ".scad", made by OpenSCAD

Fact: I just ran "sudo updatedb" and generated a new date just now,
/var/cache/locate/locatedb.n
so that s/b uptodate.
Al of those files should be spit out by:
"locate *.scad" issued from an xfce terminal
but I get:
gene@coyote:~$ locate *.scad
/home/gene/vac_ctrl_box.scad
/home/gene/xhome_cable.scad

Acc an ls -R|wc -l  there are
433179
files in my /home/gene directory

so locate isn't working as I think it should.
try find but it finds the whole my whole local net:
gene@coyote:~$ find .scad .  |wc -l
find: ‘.scad’: No such file or directory
1176532

What am I doing wrong?


find . -name '*.scad'|wc -l

--
It's not easy to be me

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

[tomas]

On Sun, Aug 27, 2023 at 02:17:06PM -0400, Jeffrey Walton wrote:

[...]

> The symlink tool works great, too:
> 
> symlink -r / | grep dangling
> 
> You can also delete them, once you verify they are dangling:
> 
> symlink -r -d /
> 
> In fact, it is a recommended post-upgrade step for Fedora. See
> .
> 
> (I'm not arguing with you. I'm just responding to the title change).

Keep those arguments coming :-)

No, seriously. We're in here for learning. I didn't even know about
`symlink'. On the contrary: the more tools in the shop, the merrier.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

[Jeffrey Walton]

On Sun, Aug 27, 2023 at 1:10 PM Jörg-Volker Peetz  wrote:
>
> to...@tuxteam.de wrote on 24/08/2023 14:00:
> >
> > A couple of days ago I was searching for dangling symlinks.
> >
> >find . -follow -lname "*"
> >
> How about
> find -L . -type l

The symlink tool works great, too:

symlink -r / | grep dangling

You can also delete them, once you verify they are dangling:

symlink -r -d /

In fact, it is a recommended post-upgrade step for Fedora. See
.

(I'm not arguing with you. I'm just responding to the title change).

Jeff

Re: dangling symlinks [ was: Re: "locate" easier to use than "find"]

[tomas]

On Sun, Aug 27, 2023 at 07:09:36PM +0200, Jörg-Volker Peetz wrote:
> to...@tuxteam.de wrote on 24/08/2023 14:00:
> > 
> > A couple of days ago I was searching for dangling symlinks.
> > 
> >find . -follow -lname "*"
> > 
> How about
>find -L . -type l

Should work, too.

Cheers
-- 
t


signature.asc
Description: PGP signature

dangling symlinks [ was: Re: "locate" easier to use than "find"]

[Jörg-Volker Peetz]

to...@tuxteam.de wrote on 24/08/2023 14:00:


A couple of days ago I was searching for dangling symlinks.

   find . -follow -lname "*"


How about
   find -L . -type l

Regards,
Jörg.

Re: "locate" easier to use than "find"

[Greg Wooledge]

> > to...@tuxteam.de (12023-08-24):
> > > Dunno. I use find nearly every day. Seeing it as "just a recursive
> > > grep" doesn't cover a fraction of its usefulness.
> > >
> > > A couple of days ago I was searching for dangling symlinks.
> > >
> > >   find . -follow -lname "*"

Wow... what a cryptic pair of options this is.  From the man page:

   -L Follow symbolic links.  When find examines or prints information
[...]
Using  -L  causes the -lname and -ilname
predicates always to return false.

And:

   The -follow option has a similar effect to -L, though it  takes  effect
   at  the  point where it appears (that is, if -L is not used but -follow
   is, any symbolic links appearing after -follow on the command line will
   be dereferenced, and those before it will not).

And:

   -follow
  Deprecated; use the -L  option  instead.   Dereference  symbolic
  links.   Implies -noleaf.  The -follow option affects only those
  tests which appear after it on the command line.  Unless the  -H
  or -L option has been specified, the position of the -follow op‐
  tion changes the behaviour of the -newer  predicate;  any  files
  listed  as  the  argument of -newer will be dereferenced if they
  are symbolic links.  The same consideration applies to -newerXY,
  -anewer and -cnewer.  Similarly, the -type predicate will always
  match against the type of the file that a symbolic  link  points
  to rather than the link itself.  Using -follow causes the -lname
  and -ilname predicates always to return false.

And:

   -lname pattern
  File is a symbolic link whose contents match shell pattern  pat‐
  tern.  The metacharacters do not treat `/' or `.' specially.  If
  the -L option or the -follow option is in effect, this test  re‐
  turns false unless the symbolic link is broken.

So that's two votes for "this can't possibly work" and one vote for
the opposite.  From within the same manual.  Yikes.

(And the POSIX manual doesn't help here, because -lname is a GNU extension.)

Re: "locate" easier to use than "find"

[Nicolas George]

Stanislav Vlasov (12023-08-24):
> Sometimes it's unexpected :-)

Then the shell prints an error and I try again. Still less time wasted
than these two mails.

Regards,

-- 
  Nicolas George

Re: "locate" easier to use than "find"

[Stanislav Vlasov]

чт, 24 авг. 2023 г. в 18:17, Nicolas George :

> > With a really large amount of files there will be overflow of process
> > environment (or too large cmdline).

> If I expect a very large amount of files, I can use it another way.

Sometimes it's unexpected :-)

-- 
Stanislav

Re: "locate" easier to use than "find"

[tomas]

On Thu, Aug 24, 2023 at 02:05:48PM +0200, Nicolas George wrote:
> to...@tuxteam.de (12023-08-24):
> > Dunno. I use find nearly every day. Seeing it as "just a recursive
> > grep" doesn't cover a fraction of its usefulness.
> > 
> > A couple of days ago I was searching for dangling symlinks.
> > 
> >   find . -follow -lname "*"
> 
> ls **/*(N@-@)
> 
> Zsh rulz.

Definitely. My point was rather to illustrate the kind of things
find can do that locate can't.

There is more than one way to do it (TM).

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: "locate" easier to use than "find"

[Nicolas George]

Stanislav Vlasov (12023-08-24):
> With a really large amount of files there will be overflow of process
> environment (or too large cmdline).

If I expect a very large amount of files, I can use it another way.

-- 
  Nicolas George

Re: "locate" easier to use than "find"

[Stanislav Vlasov]

чт, 24 авг. 2023 г. в 17:06, Nicolas George :
>
> to...@tuxteam.de (12023-08-24):
> > Dunno. I use find nearly every day. Seeing it as "just a recursive
> > grep" doesn't cover a fraction of its usefulness.
> >
> > A couple of days ago I was searching for dangling symlinks.
> >
> >   find . -follow -lname "*"
>
> ls **/*(N@-@)

With a really large amount of files there will be overflow of process
environment (or too large cmdline).
locate and find does not store filenames in memory.

-- 
Stanislav

Re: "locate" easier to use than "find"

[Nicolas George]

to...@tuxteam.de (12023-08-24):
> Dunno. I use find nearly every day. Seeing it as "just a recursive
> grep" doesn't cover a fraction of its usefulness.
> 
> A couple of days ago I was searching for dangling symlinks.
> 
>   find . -follow -lname "*"

ls **/*(N@-@)

Zsh rulz.

Regards,

-- 
  Nicolas George

Re: "locate" easier to use than "find"

[tomas]

On Thu, Aug 24, 2023 at 01:52:28PM +0200, Oliver Schoede wrote:

[...]

> Have basically stopped using traditional 'find' outside of scripts, as
> always thought I was about the last one [...]

Dunno. I use find nearly every day. Seeing it as "just a recursive
grep" doesn't cover a fraction of its usefulness.

A couple of days ago I was searching for dangling symlinks.

  find . -follow -lname "*"

did the trick.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: "locate" easier to use than "find"

[Oliver Schoede]

On Mon, 21 Aug 2023 15:56:11 +0200
 wrote:

>On Mon, Aug 21, 2023 at 03:19:19PM +0200, Roger Price wrote:
>> On Mon, 21 Aug 2023, Hans wrote:
>> 
>> > find .mozilla -name favicons.sqlite -ls
>> >  1512492   2144 -rw-r--r--   1 myusername myusernama  2195456 Aug
>> > 21 13:29 .mozilla/firefox/gs0gkgv2.default/favicons.sqlite 1515049
>> >    260 -rw-r--r--   1 myusername myusername   262144 Aug 18 22:36
>> > .mozilla/firefox/th3dv2jy.default-1461749950404/favicons.sqlite
>> 
>> For me command "locate" is easier to use than "find":
>
>They do different things. Locate is much faster, but it only looks
>into file names. Find can do nearly everything, like looking into
>file metadata ("show me all files younger than 12 days" or "owned
>by www-data"), running external programs (e.g. grep), yadda, yadda.
>
>To each job its tool.
>
>Cheers

Have basically stopped using traditional 'find' outside of scripts, as
always thought I was about the last one. Replaced with 'fd-find' which
really is simpler/more intuitive, sometimes actually faster. Quite
typical case where ~20% of the functionality will be doing the trick
90% of the time, in less time, and to me that already looks more like
99%. Especially on single user systems. I'm feeling rather more sorry
to say it's the same with 'ag', better known as the silversearcher,
another one of those long-serving workhorses that by the way is slated
for being dropped from Debian in just a couple of days: no longer
maintained, long dead upstream. I've used it for heavy grepping about
everywhere and for so many years. Most obvious replacement in this case
apparently 'ripgrep', also Rust of course. Has a few more edges I find
a little weird but got comfortable in a matter of a days anyhow. It's
all similar enough, about the hardest part is getting the actual
commands right: never a big fan of aliases I still regularly type
'find' instead of 'fd', it's muscle memory. ;)

Meanwhile traditional (m)locate got itself replaced with plocate, it
wasn't always that fast! Old things go, new arrive, I'm still using
bash though. Sorry for going off on another tangent. If anyone is still
using 'ag', just consider the options. And yes, GNU 'find' is
overcomplicated, I've long made do with a couple of shell functions
just to fight the repetition.


Oliver

Re: "locate" easier to use than "find"

[tomas]

On Mon, Aug 21, 2023 at 06:45:16PM +0100, Brian wrote:

[...]

> plocate-updatedb.service and plocate-updatedb.timer take care of
> that for me. :)

I admit to accepting some help from trusty cron :)

> > Tools, jobs and that :)
> 
> Indeed.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: "locate" easier to use than "find"

[mick.crane]

On 2023-08-21 17:21, to...@tuxteam.de wrote:

On Mon, Aug 21, 2023 at 02:50:07PM +, Michael Kjörling wrote:

On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de:
>> For me command "locate" is easier to use than "find":
>
> They do different things. Locate is much faster, but it only looks
> into file names. Find can do nearly everything, like looking into
> file metadata ("show me all files younger than 12 days" or "owned
> by www-data"), running external programs (e.g. grep), yadda, yadda.

Another downside of locate is that it relies on its database being up
to date.

Depending on what you're trying to do, they may both be equally
useful, or one may be far more useful than the other.


Don't get me wrong. I /do/ use both, and take care that the locate
database is up-to-date.

Tools, jobs and that :)


When you imagine what it must be doing is amazing how quick updatedb is.

mick

Re: "locate" easier to use than "find"

[tomas]

On Mon, Aug 21, 2023 at 02:50:07PM +, Michael Kjörling wrote:
> On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de:
> >> For me command "locate" is easier to use than "find":
> > 
> > They do different things. Locate is much faster, but it only looks
> > into file names. Find can do nearly everything, like looking into
> > file metadata ("show me all files younger than 12 days" or "owned
> > by www-data"), running external programs (e.g. grep), yadda, yadda.
> 
> Another downside of locate is that it relies on its database being up
> to date.
> 
> Depending on what you're trying to do, they may both be equally
> useful, or one may be far more useful than the other.

Don't get me wrong. I /do/ use both, and take care that the locate
database is up-to-date.

Tools, jobs and that :)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: "locate" easier to use than "find"

[Michael Kjörling]

On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de:
>> For me command "locate" is easier to use than "find":
> 
> They do different things. Locate is much faster, but it only looks
> into file names. Find can do nearly everything, like looking into
> file metadata ("show me all files younger than 12 days" or "owned
> by www-data"), running external programs (e.g. grep), yadda, yadda.

Another downside of locate is that it relies on its database being up
to date.

Depending on what you're trying to do, they may both be equally
useful, or one may be far more useful than the other.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: "locate" easier to use than "find"

[tomas]

On Mon, Aug 21, 2023 at 03:19:19PM +0200, Roger Price wrote:
> On Mon, 21 Aug 2023, Hans wrote:
> 
> > find .mozilla -name favicons.sqlite -ls
> >  1512492   2144 -rw-r--r--   1 myusername myusernama  2195456 Aug 21 13:29 
> > .mozilla/firefox/gs0gkgv2.default/favicons.sqlite
> >  1515049    260 -rw-r--r--   1 myusername myusername   262144 Aug 18 22:36 
> > .mozilla/firefox/th3dv2jy.default-1461749950404/favicons.sqlite
> 
> For me command "locate" is easier to use than "find":

They do different things. Locate is much faster, but it only looks
into file names. Find can do nearly everything, like looking into
file metadata ("show me all files younger than 12 days" or "owned
by www-data"), running external programs (e.g. grep), yadda, yadda.

To each job its tool.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: locate something not exist

[Huang, Tao]

off-topic:

mlocate have some advantages over locate.
it does a partial scan on modified files only, which makes it's
updatedb much faster and disk friendly.

u may already be using it if u have it installed,
since mlocate has a higher score in the update-alternatives system
than the original locate.


Cheers,

Tao
--
http://huangtao.me/
http://www.google.com/profiles/UniIsland

School of Mathematical Science
Peking University


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi=cj3zb1zq7i11ou0rncm77kd8...@mail.gmail.com

Re: locate something not exist

[teddieeb]

I believe you need to run

#updatedb

If I am not mistaken (updatedb may work for different search command if memory 
is faulty) 

But if I'm not mistaken, updatedb will refresh the database locate uses to find 
results...

TeddyB

-Original Message-
From: lina lina.lastn...@gmail.com
Date: Thu, 28 Apr 2011 12:55:38 
To: debian-user@lists.debian.org
Subject: locate something not exist

Hi,

when I located fglrx

which has been purged,

but it still showed me lots
such as

/var/lib/dpkg/info/fglrx-glx.preinst
/var/lib/dpkg/info/fglrx-modules-dkms.list
/var/lib/dpkg/info/fglrx-modules-dkms.md5sums
/var/lib/dpkg/info/fglrx-modules-dkms.postinst
/var/lib/dpkg/info/fglrx-modules-dkms.prerm
/var/lib/dpkg/info/fglrx-source.list
/var/lib/dpkg/info/fglrx-source.md5sums
/var/lib/update-rc.d/fglrx-atieventsd

when I checked further, found

# more /var/lib/dpkg/info/fglrx-source.md5sums
/var/lib/dpkg/info/fglrx-source.md5sums: No such file or directory
# more /var/lib/dpkg/info/fglrx-driver.preinst
/var/lib/dpkg/info/fglrx-driver.preinst: No such file or directory
# more /etc/modprobe.d/fglrx-driver.conf
/etc/modprobe.d/fglrx-driver.conf: No such file or director

so the locate has some problems?


--
Thanks and best regards,

lina


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktinjedycmtcb_i6nwvcr+kcc6mh...@mail.gmail.com

Re: locate something not exist

[lina]

Thanks,

it works,


On Thu, Apr 28, 2011 at 1:06 PM,  teddi...@tmo.blackberry.net wrote:

 I believe you need to run

 #updatedb

 If I am not mistaken (updatedb may work for different search command if 
 memory is faulty)

 But if I'm not mistaken, updatedb will refresh the database locate uses to 
 find results...

 TeddyB

 -Original Message-
 From: lina lina.lastn...@gmail.com
 Date: Thu, 28 Apr 2011 12:55:38
 To: debian-user@lists.debian.org
 Subject: locate something not exist

 Hi,

 when I located fglrx

 which has been purged,

 but it still showed me lots
 such as

 /var/lib/dpkg/info/fglrx-glx.preinst
 /var/lib/dpkg/info/fglrx-modules-dkms.list
 /var/lib/dpkg/info/fglrx-modules-dkms.md5sums
 /var/lib/dpkg/info/fglrx-modules-dkms.postinst
 /var/lib/dpkg/info/fglrx-modules-dkms.prerm
 /var/lib/dpkg/info/fglrx-source.list
 /var/lib/dpkg/info/fglrx-source.md5sums
 /var/lib/update-rc.d/fglrx-atieventsd

 when I checked further, found

 # more /var/lib/dpkg/info/fglrx-source.md5sums
 /var/lib/dpkg/info/fglrx-source.md5sums: No such file or directory
 # more /var/lib/dpkg/info/fglrx-driver.preinst
 /var/lib/dpkg/info/fglrx-driver.preinst: No such file or directory
 # more /etc/modprobe.d/fglrx-driver.conf
 /etc/modprobe.d/fglrx-driver.conf: No such file or director

 so the locate has some problems?


 --
 Thanks and best regards,

 lina


 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/banlktinjedycmtcb_i6nwvcr+kcc6mh...@mail.gmail.com





-- 
Thanks and best regards,

lina


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktikxr97ws_pgjstx9atsts9wntn...@mail.gmail.com

Re: locate something not exist

[teddieeb]

Your welcome, glad I was actually able to help somebody ;P

TeddyB


-Original Message-
From: lina lina.lastn...@gmail.com
Date: Thu, 28 Apr 2011 13:09:32 
To: debian-user@lists.debian.org
Cc: Debian Listsdebian-user@lists.debian.org
Subject: Re: locate something not exist

Thanks,

it works,


On Thu, Apr 28, 2011 at 1:06 PM,  teddi...@tmo.blackberry.net wrote:

 I believe you need to run

 #updatedb

 If I am not mistaken (updatedb may work for different search command if 
 memory is faulty)

 But if I'm not mistaken, updatedb will refresh the database locate uses to 
 find results...

 TeddyB

 -Original Message-
 From: lina lina.lastn...@gmail.com
 Date: Thu, 28 Apr 2011 12:55:38
 To: debian-user@lists.debian.org
 Subject: locate something not exist

 Hi,

 when I located fglrx

 which has been purged,

 but it still showed me lots
 such as

 /var/lib/dpkg/info/fglrx-glx.preinst
 /var/lib/dpkg/info/fglrx-modules-dkms.list
 /var/lib/dpkg/info/fglrx-modules-dkms.md5sums
 /var/lib/dpkg/info/fglrx-modules-dkms.postinst
 /var/lib/dpkg/info/fglrx-modules-dkms.prerm
 /var/lib/dpkg/info/fglrx-source.list
 /var/lib/dpkg/info/fglrx-source.md5sums
 /var/lib/update-rc.d/fglrx-atieventsd

 when I checked further, found

 # more /var/lib/dpkg/info/fglrx-source.md5sums
 /var/lib/dpkg/info/fglrx-source.md5sums: No such file or directory
 # more /var/lib/dpkg/info/fglrx-driver.preinst
 /var/lib/dpkg/info/fglrx-driver.preinst: No such file or directory
 # more /etc/modprobe.d/fglrx-driver.conf
 /etc/modprobe.d/fglrx-driver.conf: No such file or director

 so the locate has some problems?


 --
 Thanks and best regards,

 lina


 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/banlktinjedycmtcb_i6nwvcr+kcc6mh...@mail.gmail.com





--
Thanks and best regards,

lina


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktikxr97ws_pgjstx9atsts9wntn...@mail.gmail.com

Re: locate something not exist

[Liam O'Toole]

On 2011-04-28, teddi...@tmo.blackberry.net teddi...@tmo.blackberry.net wrote:

 I believe you need to run

 #updatedb

 If I am not mistaken (updatedb may work for different search command if 
 memory is faulty) 

 But if I'm not mistaken, updatedb will refresh the database locate uses to 
 find results...


If you are unable to run updatedb, use 'locate -e' when searching. Then
only the names of files which still exist will be printed.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnirhuou.enl.liam.p.otoole@dipsy.tubbynet

Re: Locate older debian packages

[Camaleón]

On Mon, 19 Jul 2010 09:29:58 +0300, Panayiotis Karabassis wrote:

 I need to downgrade a package due to a bug. However the older package
 version is no longer available from apt. Is there a way to find the
 older .deb? If it is of any importance I am searching for the eclipse
 version prior to 3.5.2-5.

http://snapshot.debian.org/binary/eclipse/

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2010.07.19.06.34...@gmail.com

Re: Locate older debian packages

[Ansgar Burchardt]

Hi,

Panayiotis Karabassis pan...@gmail.com writes:

 I need to downgrade a package due to a bug. However the older package
 version is no longer available from apt. Is there a way to find the
 older .deb? If it is of any importance I am searching for the eclipse
 version prior to 3.5.2-5.

Try snapshot.debian.org.  And remember to report the bug so it gets
fixed ;)

Regards,
Ansgar


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874ofw0yj9@marvin.43-1.org

Re: Locate older debian packages

[Panayiotis Karabassis]

Thank you both. And the bug is already reported.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4c43f436.4010...@gmail.com

Re: Locate older debian packages

[Panayiotis Karabassis]

Thank you both. And the bug is already reported.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4c43f432.6000...@gmail.com

Re: Locate older debian packages

[Klistvud]

Dne, 19. 07. 2010 08:29:58 je Panayiotis Karabassis napisal(a):
I need to downgrade a package due to a bug. However the older package  
version is no longer available from apt. Is there a way to find the  
older .deb? If it is of any importance I am searching for the eclipse  
version prior to 3.5.2-5.


snapshot.debian.org

--
Regards,

Klistvud
Certifiable Loonix User #481801
http://bufferoverflow.tiddlyspot.com


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1279525501.2279...@compax

Re: locate

[Thorsten Haude]

Moin,

* Markus Henrich [EMAIL PROTECTED] [2004-01-11 11:13]:
Ich benutze woody und wenn ich den Befehl locate aufrufe, erhalte ich
folgende Fehlermeldung:

locate: /var/lib/locate/locatedb: No such file or directory

Was läuft da falsch und wie kann ich den Fehler beseitigen?

Ich würde erstmal spontan versuchen, die Datenbank aufzubauen:
su -c updatedb


Thorsten
-- 
You're not supposed to be so blind with patriotism that you can't face
reality. Wrong is wrong, no matter who does it or who says it.
- Malcolm X


pgp0.pgp
Description: PGP signature

Re: locate

[Thorsten von Plotho-Kettner]

Am Sonntag, 11. Januar 2004 11:13 schrieb Markus Henrich:

 Ich benutze woody und wenn ich den Befehl locate aufrufe, erhalte ich
 folgende Fehlermeldung:

 locate: /var/lib/locate/locatedb: No such file or directory

 Was läuft da falsch und wie kann ich den Fehler beseitigen?

man slocate

-u generiert dir eine Datenbank ab /

Weitere Infos findest du in der Manpage.

Gruß,

Thorsten


--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: locate

[Norbert Tretkowski]

* Markus Henrich wrote:
 Ich benutze woody und wenn ich den Befehl locate aufrufe, erhalte
 ich folgende Fehlermeldung:
 
 locate: /var/lib/locate/locatedb: No such file or directory
 
 Was läuft da falsch und wie kann ich den Fehler beseitigen?

Die locatedb wird eigentlich taeglich via Cron aktualisiert. Sollte
dein PC nicht durchgehen laufen, schau dir mal anacron an, der startet
die Cronjobs nicht zu bestimmten Zeiten, sondern nachdem dein PC eine
gewisse Zeit lief.

Norbert


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: locate

[M.Kiberu]

Also, das einfachste wäre, wenn du dich als root anmeldest und updatedb ausführst. 
Damit wird praktisch das Index neu generiert.

Danach kannst du 'locate gesuchtes' ausführen mit dem akktuelsten Index.
Das solltest du übringes ruhig mal machen, wenn du eine Datei mal nicht finden 
solltest -der Index könnte ja veraltet sein!

Viel Erfolg,
Michael

On Sonntag Januar 11th 2004, Markus Henrich wrote:

 Hallo!
 Ich benutze woody und wenn ich den Befehl locate aufrufe, erhalte ich
 folgende Fehlermeldung:
 locate: /var/lib/locate/locatedb: No such file or directory
 Was läuft da falsch und wie kann ich den Fehler beseitigen?
 Grüße
 Markus
 --
 Haeufig gestellte Fragen und Antworten (FAQ):
 http://www.de.debian.org/debian-user-german-FAQ/
 Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
 mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)


--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: locate

[Sebastian Inacker]

Hallo.

On Mon, Jan 12, 2004 at 12:38:02AM +0100, M.Kiberu wrote:
[ /var/lib/locate/locatedb fehlt beim Aufruf von 'locate' ]
 Also, das einfachste wäre, wenn du dich als root anmeldest und
 updatedb ausführst. Damit wird praktisch das Index neu generiert.

Allerdings wird dann der Index mit root-Rechten erstellt. Das heisst,
dass User A auch Dateien von User B im Index finden kann, die er an
sich gar nicht zu sehen bekommen duerfte (Dateirechte des $HOME
o.ae.). 

Im Paket findutils gibt es ein /etc/cron.daily/find - das wechselt
fuer die Suche zum User nobody und laesst auch ein paar Dinge weg
(NFS, CDs, /tmp, ...). Was nobody im $HOME von User B nicht finden
kann/darf, findet User A dann auch nicht. (Ja, ich hatte updatedb
selbst mal als root von Hand aufgerufen... ;-). )

P.S.: Anacron ist eine nette Sache fuer Rechner, die nicht 24h laufen.
Vermutlich lief der Rechner nie, wenn der Cronjob dran gewesen
waere...

Tschuess,
  Sebastian


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Locate não funciona

[Claudio Clemens]

2003-08-07, 09:17 -0300, Savio Ramos:
 Olá,
 
 No Gnome2.2 existe um programa em Ações-Procurar Arquivos que não está 
 funcionando. A mensagem de erro está abaixo:
 
 Os seguintes erros foram encontrados durante a procura.
 /usr/bin/locate: /var/cache/locate/locatedb: Arquivo ou diretório não 
 encontrado
 
 Obs: o arquivo locate está no dirtetório mencionado.
 
 Alguma luz?

Para sanar AGORA esse problema, rode primeiro um updatedb, que cria o
locatedb.

Para sanar para sempre, instale o anacron, que ele é responsável para
que o updatedb seja feito uma vez por dia.

apt-install anacron

Até

Claudio

-- 
+- .''`. ---| Claudio Clemens in Germany now |--| Sid |---+
| : :' :   asturio at gmx.netGNU/Linux User #79942|
| `. `'To C or not to C? That's the question!   |
|   `- YE GODS, I HAVE FEET??! - Userfriendly  |
Bad command or file name. Go sit in corner.


pgp0oSaD3x8NN.pgp
Description: PGP signature

Re: Locate não funciona

[Savio Ramos]

On Thu, 7 Aug 2003 14:45:58 +0200
Claudio Clemens [EMAIL PROTECTED] wrote:

 Para sanar AGORA esse problema, rode primeiro um updatedb, que cria o
 locatedb.

Funcionou beleza,
brigadúu.

Re: locate y cron

[Alejandro Pinazo]

Hola:

Hector Miuler escribió:

 Hola amigos, tengo una duda con locate, pues l principio cundo recien
 estaba instalado mi woody no me salia nada con locate, bueno buscando
 en el a ecotre algo referente a updatedb y recién pude usar el locate,
 ahora supongo que locate no se esta actualizando automaticamente, me
 imgino que hara falta colocarlo en el cron, buscando en etc/cron... no
 encontre algun  archivo con el nombre de locate, solo medusa, find,
 etc. bueno detro de /etc/cro.daily/find 
 
 [EMAIL PROTECTED]:/mnt/Instaladores-Linux/Utilidades$ cat
 /etc/cron.daily/find
 #! /bin/sh
 #
 # cron script to update the `find.codes' database.
 #
 # Written by Ian A. Murdock [EMAIL PROTECTED] and 
 #Kevin Dalley [EMAIL PROTECTED]
 if [ -f /etc/updatedb.conf ]; then
   . /etc/updatedb.conf
 fi
 cd /  updatedb --localuser=nobody 2/dev/null
 
 
 y dentro de updtedb.conf
 
 # This file sets environment variables which are used by updatedb
 
 # filesystems which are pruned from updatedb database
 PRUNEFS=NFS nfs afs proc smbfs autofs auto iso9660 ncpfs coda devpts
 ftpfs
 export PRUNEFS
 # paths which are pruned from updatedb database
 PRUNEPATHS=/tmp /usr/tmp /var/tmp /afs /amd /alex /var/spool
 export PRUNEPATHS
 # netpaths which are added
 NETPATHS=
 export NETPATHS
 
 como puedo hacer par que locate se actualice solo, ¿biene por defecto
 configurado para woody?

Instala el paquete anacron y él sólo se actualizará diariamente cuando
conectes tu equipo.

Un saludo.

Re: locate ne fonctionne plus

[Frédéric Bothamy]

On Fri, Oct 18, 2002 at 02:54:54PM +0200, Didier Chalm wrote:
 On Thursday 17 October 2002 12:04, eric.delassus wrote:
 
  Oui et le problème est le suivant lorsque je fais un locate ou un updatedb
  je reviens immédiatement à l'invite sans aucun message d'erreur.
 
 Tu ne serais pas passé en ext3 récemment ? Tu n'aurais pas ta partition 
 racine (/) montée en 'auto' dans ton /etc/fstab ?
 
 Si c'est le cas, vérifie dans le fichier /etc/updatedb.conf, à la variable 
 PRUNEFS, si le mot-clé 'autofs' est présent. Si oui, il faut l'en retirer...
 
 J'ai mis un temps fou à trouver ça chez moi il y a quelque temps... ;)

Pourtant c'est dans le BTS (#113139, #119603, #132430, #144649 et
#129121).

Fred

Re: locate ne fonctionne plus

[Didier Chalm]

On Thursday 17 October 2002 12:04, eric.delassus wrote:

 Oui et le problème est le suivant lorsque je fais un locate ou un updatedb
 je reviens immédiatement à l'invite sans aucun message d'erreur.

Tu ne serais pas passé en ext3 récemment ? Tu n'aurais pas ta partition 
racine (/) montée en 'auto' dans ton /etc/fstab ?

Si c'est le cas, vérifie dans le fichier /etc/updatedb.conf, à la variable 
PRUNEFS, si le mot-clé 'autofs' est présent. Si oui, il faut l'en retirer...

J'ai mis un temps fou à trouver ça chez moi il y a quelque temps... ;)

HTH,

-- 
  [EMAIL PROTECTED]   EPSHOM
  Service Informatique   BREST - FRANCE

RE: locate ne fonctionne plus

[STOJICEVIC Edi EXPSIA]

Depuis quelques jours la commande locate ne fonctionne plus sur ma sid, 

salut,

as-tu fait un updatedb ?

@+

-- 
 .''`.   Debian GNU/Linux 3.0 released !   (\___/)
: :'  :Use it ! ;) (='.'=)
`. `~'   http://www.debianworld.org()_()
  `- 
*

Ce message et toutes les pieces jointes (ci-apres le message) sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite. 
Tout message electronique est susceptible d'alteration. 
La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de 
ce message s'il a ete altere, deforme ou falsifie.



This message and any attachments (the message) are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited. 
E-mails are susceptible to alteration.   
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be 
liable for the message if altered, changed or falsified. 

*

Re: locate ne fonctionne plus

[Erwan David]

Le Thu 17/10/2002, eric.delassus disait
 Depuis quelques jours la commande locate ne fonctionne plus sur ma sid, 
 est-ce-dû à un bug qui sera corrigé d'ici peu où cela peut-il provenir d'un 
 pb de config sur ma machine ?

ça veut dire quoi ne fonctionne plus ? il y a un message d'erreur ?

-- 
Erwan

[LONG] Re: locate ne fonctionne plus

[Yannick Roehlly]

Bonjour la liste,

Je me permet de répondre à Georges qui à lancer un
trol###débat...

Personnellement, j'utilise sid parce que je suis atteint de
dernièreversionite aiguë (on appelle ça les early-adopters) et
que d'une part ma machine personnelle n'est pas si importante que
ça et d'autre part je pense (présomption ?) que je suis capable
de régler la majeure partie des problèmes. De plus, ça me permet
de participer modestement à Debian par des rapport de bug[1].

Néanmoins, je suis _tout à fait d'accord_ pour dire qu'il ne faut
pas conseiller sid à des débutants surtout que woody est encore
rélativement récente et que de toute façon il y a sarge qui ne
doit pas avoir de problèmes[2].

Cependant, je ne suis pas d'accord avec ce que dit Georges :

 et bien, il joue **tout seul**, non?

Est-ce que parce qu'on utilise sid on n'est pas un debian-user ?

Dans son mail[3], Éric disait :

 Depuis quelques jours la commande locate ne fonctionne plus sur ma
 sid,

Je ne vois qu'un debian-user(sid) qui pose une question à
d'autres debian-user(sid) pour savoir si chez eux locate
fonctionne.

Par contre je pense que l'on aurait pu faire une autre critique à
son message :

 est-ce-dû à un bug qui sera corrigé d'ici peu

As-tu vérifié sur le BTS de Debian ?
As-tu l'intention de faire un rapport de bug ou attends-tu que
cela se règle tout seul ?

Par contre une question du style Chez moi sous sid locate ne
fonctionne pas, je n'ai rien vu sur le BTS, pensez-vous que ça
soit un bug (sous-entendu est-ce que ça fonctionne chez vous
avec le même paquet) ou est-ce que je fait un rapport de bug ?
ne m'aurait pas du tout choqué ici.

J'ai déjà eu une discussion similaire avec Nicolas. Pour moi,
debian-devel est destinée aux développeurs pour parler entre-eux
ou alors pour contacter les développeurs à propos d'un bug _une
fois que celui-ci a été identifié, en plus du BTS[4]. Peut-être
suis-je dans l'erreur ? (je vais retourne sur la page Debian
voir la description des listes...)

Peut-être faudrait-il alors créer une liste
debian-users-sid-french ?

Des avis ?

Communautairement votre,

Yannick

[1] Même si pour l'instant j'ai rencontré très peu de bugs et que
la majeure partie étaient déjà signalés sur le BTS...

[2] Enfin, vu le peu de problèmes de sid, je ne pense pas qu'il
en reste beaucoup pour sarge...

[3] Que je n'ai d'ailleurs pas reçu de la liste autrement qu'avec
la réponse de Georges... ?

[4] Le problème est que poster sur debian-devel-french a peu de
chance de toucher un développeur islandais ;-)

-- 
Ramer dans le sens du courant fait rire les crocodiles.
Proverbe Africain

Re: [LONG] Re: locate ne fonctionne plus

[Georges Mariano]

On Thu, 17 Oct 2002 12:52:58 +0200
Yannick Roehlly [EMAIL PROTECTED] wrote:

 Bonjour la liste,
 
 Je me permet de répondre à Georges qui à lancer un
 trol###débat...

un petit alors... c'est une idée qui revient assez souvent ici que
pour Sid, l'utilité/efficacité de la liste est incertaine...

 Personnellement, j'utilise sid parce que je suis atteint de

ça se soigne ;-) reviens en sarge/woody ;-)

 Cependant, je ne suis pas d'accord avec ce que dit Georges :
 
  et bien, il joue **tout seul**, non?

ça m'apprendra a vouloir faire bref, 

le sens est il se retrouve un peu isolé dans son bonheur ;-)
(conséquence de son comportement, et visiblement il l'assume), 

le sens **n'était pas** ben alors tu te dem^Hbrouille tout seul
(sanction de la collectivité en réaction)

 
 Est-ce que parce qu'on utilise sid on n'est pas un debian-user ?

évidemment que oui

 Communautairement votre,
Idem

-- 
mailto:[EMAIL PROTECTED] tel: (33) 03 20 43 84 06   
INRETS, 20 rue Élisée Reclus fax: (33) 03 20 43 83 59   
BP 317 -- 59666 Villeneuve d'Ascq   
http://www3.inrets.fr/estas/mariano

Re: locate ne fonctionne plus - don't panic

[eric.delassus]

Désolé d'avoir déclanché un début de polémique en posant une question qui se 
voulait initialement très innocente...
Mon intention était en effet de savoir si d'autres rencontraient le même 
problème, j'aurais pu en effet pousser un peu plus loin les recherches, mais 
par manque de temps, j'ai choisi la facilité... Je m'en excuse.
Je pourrais certes utiliser une woody mais étant comme Yannick atteint de 
dernièreversionite aiguë pour ma machine perso qui, elle non plus, n'est pas 
si importante que cela, je préfère la sid.
D'autre part ne passant pas mes journées à encombrer la liste avec mes petits 
problèmes perso que j'essaie le plus souvent de règler tout seul, je pense 
qu'il faut avoir le sens de la mesure et ne pas s'affoler pour si peu.

Cordialement
-- 
Eric Delassus - Cogito - http://perso.wanadoo.fr/eric.delassus

ULiCe - Association des utilisateurs de linux et des logiciels libres du 
centre -
http://ulice.tuxfamily.org

Re: [LOCATE]

[Cyrille Chepelov]

Le Mon, Feb 25, 2002, à 04:46:04PM +0100, Adeimantos a écrit:
 
 Lorsque je lance la commande locate sous Woody, j'ai le message :
 /var.lib/locate/locatedb aucun message de ce type.
 Mais rien ne correspond à un paquet locate ou locatedb. Comment jouir
 de cette commande? JP

apt-cache search locate | grep locate


A++

-- 
Grumpf.

Re: [LOCATE]

[Nicolas SABOURET]

Adeimantos wrote:
 
 Lorsque je lance la commande locate sous Woody, j'ai le message :
 /var.lib/locate/locatedb aucun message de ce type.
 Mais rien ne correspond à un paquet locate ou locatedb. Comment jouir
 de cette commande? JP

updatedb sous root.
-- 
Nicolas SABOURET
LIMSI-CNRS, BP133, 91403 Orsay, France
http://www.limsi.fr/Individu/nico

Re: [LOCATE]

[Olivier Garet]

et après, sous root, taper updatedb
pour mettre la base de données à jour.

man locate est aussi ton ami.

A+

Olivier

Re: [LOCATE]

[Christophe « CHiPs » PETIT]

le lun 25-02-2002 à 16:51, Nicolas SABOURET a écrit :
 updatedb sous root.

Un autre bon moyen est d'installer le paquet anacron, et d'attendre
quelques minutes que le script /etc/cron.daily/find ait fait son office
(et il le fera une fois par jour ensuite)

Voilà,

-- 
Christophe «CHiPs» PETIT [EMAIL PROTECTED] http://chips.free.fr/
Linux-Nantes: partagez votre savoir http://www.linux-nantes.fr.eu.org/
Debian: When Code Matters More Than Commercials http://www.debian.org/  
[Do clones have navels?]

Re: [LOCATE]

[Adeimantos]

On Mon, 25 Feb 2002 16:45:19 +0100
Cyrille Chepelov [EMAIL PROTECTED] a écrit:

 Le Mon, Feb 25, 2002, à 04:46:04PM +0100, Adeimantos a écrit:
  
  Lorsque je lance la commande locate sous Woody, j'ai le message :
  /var.lib/locate/locatedb aucun message de ce type.
  Mais rien ne correspond à un paquet locate ou locatedb. Comment
  jouir de cette commande? JP
 
 apt-cache search locate | grep locate
 


Autant pour moi. J'avais complètement oublié de faire un updatedb avant
d'utiliser la commande : c'est slocate qui fait cet updatedb
automatiquement qui m'y a fait penser. JP

PS Merci Cyrille pour la commande.
-- 
«Few discoveries are more irritating than 
those which discover the pedigree of ideas.»
John Edward Emerich Dalberg,Lord ACTON

Re: [LOCATE]

[Adeimantos]

On Mon, 25 Feb 2002 16:46:04 +0100
Adeimantos [EMAIL PROTECTED] a écrit:

 
 Lorsque je lance la commande locate sous Woody, j'ai le message :
 /var.lib/locate/locatedb aucun message de ce type.
 Mais rien ne correspond à un paquet locate ou locatedb. Comment jouir
 de cette commande? JP



Merci à tous pour ce updatedb que je connaissais, mais qui m'est
complètement sorti de l'esprit. Merci pour anacron.
JP

-- 
«Few discoveries are more irritating than 
those which discover the pedigree of ideas.»
John Edward Emerich Dalberg,Lord ACTON

Re: locate MERCI

[Jean-Michel OLTRA]

On dimanche 13 jan 2002, h. suvigny wrote:
   
 MERCI à tous pour vos réponses, ça marche et en plus j'ai installé anacron
 (suite à vos mails)

Tu dois avoir le paquet slocate pour 'secure locate'. Il assure que les
users ne pourront faire un locate que là où ils ont le droit de le faire.

-- 
jean-michel

Re: locate MERCI

[h . suvigny]

On Sat, 12 Jan 2002 22:53:57 +0100
h.suvigny [EMAIL PROTECTED] wrote:

Bonjour à tous
  
  J'avoue que je n'osais pas poser la question, je pensais que cela
venais
  de moi, mais je ne trouve pas la réponse.
  
  J'utilise Debian 2.2.r3
  
  Chaque fois que je tape locate dans un term j'ai la meme réponse
  
  /ex: locate latex
  
  locate: /var/lib/locate/locatedb: aucun fichier ou répertoire de ce
type
  
MERCI à tous pour vos réponses, ça marche et en plus j'ai installé anacron
(suite à vos mails)

Amicalement 

Hervé

-- 
Have a nice Linux

E-mail: [EMAIL PROTECTED]
Site internet:  http://passionachat.free.fr


pgpPGjDqtH20h.pgp
Description: PGP signature

Re: locate

[VALLIET Manu]

Le 12/01/02, h.suvigny a ecrit:



  Bonjour à tous,

  J'avoue que je n'osais pas poser la question, je pensais que cela venais
  de moi, mais je ne trouve pas la réponse.

  J'utilise Debian 2.2.r3

  Chaque fois que je tape locate dans un term j'ai la meme réponse

  /ex: locate latex

  locate: /var/lib/locate/locatedb: aucun fichier ou répertoire de ce type

  Il est exacte que je n'ai pas de locatedb

  Comment pourrai je trouver la solution ??

  Amicalement

  Hervé

Dans la SID (mais j'imagine que c'est pareil en patate), le fichier est
mis à jour quotidiennement via /etc/cron.daily/find.
Pour lancer la construction de la base manuellement, suffit de taper
updatedb (avec p'tet quelques arguments).
Si le cron est pas lancé, c'est que ta machine est pas tout le temps
allumée (en général, c'est vers 6H du mat' que tout se lance), ce qui est
pas forcément un mal. La solution, c'est d'installer anacron, qui fait les
cron.daily et Cie dès qu'il le peut (en général, pas longtemps après le
boot, ce qui peut se révéler gavant, ça fait un peu ramer), ou bien de
changer la date d'execution du cron.daily dans /etc/crontab.

Sinon, y'a aussi dlocate qu'est sympa.

--
Manu

Re: locate

[Camille Dominique]

On Sat, Jan 12, 2002 at 10:53:57PM +0100, h.suvigny wrote:
  Chaque fois que je tape locate dans un term j'ai la meme réponse
  /ex: locate latex
  locate: /var/lib/locate/locatedb: aucun fichier ou répertoire de ce type
  Il est exacte que je n'ai pas de locatedb
  Comment pourrai je trouver la solution ??

lance la commande 'updatedb' en tant que root
après quelques minutes (selon la taille et la vitesse de tes disques),
une locatedb aura été créée dans /var/lib/locate, et la commande locate
donnera des résultats.

D'habitude sur un système debian, la commande updatedb est lancée
automatiquement par cron à une certaine heure. Si ton ordinateur n'est
pas allumé en permanence, je te conseille vivement d'installer le paquet
'anacron', qui s'occupe de tous les jobs cron en attente peu après le 
démarrage de ta bécanne.

  Amicalement

pareil :-)
-- 
Camille 
   simply the most linux - http://www.debian.org

Re: locate

[Laurent Martelli]

 hervé == h suvigny [EMAIL PROTECTED] writes:

  hervé  Bonjour à tous,
 
  hervé  J'avoue que je n'osais pas poser la question, je pensais que
  hervé cela venais de moi, mais je ne trouve pas la réponse.
 
  hervé  J'utilise Debian 2.2.r3
 
  hervé  Chaque fois que je tape locate dans un term j'ai la meme
  hervé réponse
 
  hervé  /ex: locate latex
 
  hervé  locate: /var/lib/locate/locatedb: aucun fichier ou
  hervé répertoire de ce type
 
  hervé  Il est exacte que je n'ai pas de locatedb
 
  hervé  Comment pourrai je trouver la solution ??

Tu dois pouvoir en créer une avec la commande updatedb. 

-- 
Laurent Martelli
[EMAIL PROTECTED]  http://www.bearteam.org/~laurent/

Re: locate

[Frédéric Bothamy]

On Sat, 12 Jan 2002 22:53:57 +0100
h.suvigny [EMAIL PROTECTED] wrote:

 
 
  Bonjour à tous,
  
  J'avoue que je n'osais pas poser la question, je pensais que cela venais
  de moi, mais je ne trouve pas la réponse.
  
  J'utilise Debian 2.2.r3
  
  Chaque fois que je tape locate dans un term j'ai la meme réponse
  
  /ex: locate latex
  
  locate: /var/lib/locate/locatedb: aucun fichier ou répertoire de ce type
  
  Il est exacte que je n'ai pas de locatedb
  
  Comment pourrai je trouver la solution ??

Lire la page de manuel de locatedb (vérifié sous woody) ?

$ man locatedb

LOCATEDB(5L) LOCATEDB(5L)

NAME
   locatedb - front-compressed file name database

DESCRIPTION
   This  manual  page  documents  the  format  of  file  name
   databases for the GNU version of locate.   The  file  name
   databases  contain  lists of files that were in particular
   directory trees when the databases were last updated.

   There can be multiple databases.  Users can  select  which
   databases locate searches using an environment variable or
   command line option; see locate(1L).  The system  adminis­
   trator  can  choose the file name of the default database,
   the frequency with which the databases  are  updated,  and
   the directories for which they contain entries.  Normally,
   file name databases are updated by  running  the  updatedb
   program periodically, typically nightly; see updatedb(1L).

Donc, il faut faire un updatedb, mais celui-ci est fait
automatiquement dans un script placé dans la crontab :
/etc/cron.daily/find, lancé à 6h25 chez moi, mais comme ma machine
n'est pas allumée à cette heure-là, ce n'est pas fait, donc je le fais
à la main quand j'en ai besoin. (je sais qu'anacron peut me le faire
mieux que cron, mais bon ...)

Fred

Re: locate/updatedb on crack

[Pat Mahoney]

  now with gimpinitl.h.
 
 gimpintl.h != gimpinit.h
 
  The other found gimp.h, which is in the same dir as gimpinit.h.  But
  it still can't locate gimpinitl.h.

Well, that's embarassing.  Stupid typos...  Maybe I'm dyslexic (is
that spelled right?, ispell flags it, no suggestions though, and I
can't think of anything else)... Yeah, that's it.  To partially save
face, I confused gimpintl.h with gimpinitl.h, not gimpintl.h and
gimpinit.h, although it might not look like that...

-- 
Pat Mahoney  [EMAIL PROTECTED]


I had no shoes and I pitied myself.  Then I met a man who had no feet,
so I took his shoes.
-- Dave Barry

Re: locate

[Antonio Castro]

On Mon, 8 May 2000, Emilio Hernández Martín wrote:

 
 Hola.
 
 Tengo un fichero que el comando 'locate' no es capaz de encontrar pero
 que sí puede encontrar 'find'. Es un fichero de cabecera de C que tampoco
 encuentra el compilador a pesar de que debería (en teoría) hacerlo pq el
 programa está probado en otro ordenador y sí que compila. Quizá sea por la
 misma razón por la que 'locate' no es capaz de hallar dicho
 fichero. No lo sé. ¿Alguien sabe a qué puede deberse esto?

locate busca en una base de datos que supuestamente se actualiza con
cierta regularidad. Haz updatedb y vuelve a usar locate. updatedb
hace algo parecido que un find para actualizar la DB. Esta BD es muy
eficiente ocupa muy poco porque usa un algoritmo de compresion de nombres
que aprovecha las similitudes entre nombres de caminos completos y localiza 
con gran rapidez cualquier  nombre.

Si el compilador no lo encuentra será por otra razon. Prueba a usar la
opción -I seguida del camino  del include.

 Muchas gracias y un saludo.
 
 Emilio.
 --  
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

Saludos 

Antonio Castro


+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
/\ /\ Ciberdroide Informatica (tienda linux)
  \\W// http://www.ciberdroide.com 
 _|0 0|_
+-oOOO--(___o___)--OOOo--+ 
|  . . . . U U . . . . Antonio Castro Snurmacher !! Nueva direccion email !! |  
| http://slug.ctv.es/~acastro.  - - - -  [EMAIL PROTECTED] | 
+()()()--()()()--+
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
(((Donde Linux)))http://www.ciberdroide.com/misc/donde/dondelinux.html
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

Re: locate

[Eduardo Urrea]

On Tue, 9 May 2000, Eduardo Urrea wrote:

  Hola.
  
  Tengo un fichero que el comando 'locate' no es capaz de encontrar pero
  que sí puede encontrar 'find'. Es un fichero de cabecera de C que tampoco
  encuentra el compilador a pesar de que debería (en teoría) hacerlo pq el
  programa está probado en otro ordenador y sí que compila. Quizá sea por la
  misma razón por la que 'locate' no es capaz de hallar dicho
  fichero. No lo sé. ¿Alguien sabe a qué puede deberse esto?
 
Prueba a poner en la linea de comandos:
$ update
$ updatedb
$ locate fichero.h
 
A ver si ahora te lo encuentra... si no te lo encuentra el compilador ...
que fichero de cabecera es :? 

*
  Eduardo Urrea Alcaraz [EMAIL PROTECTED]
http://www.hispasecurity.com
Seguridad Informatica
*

Re: locate

[Javier Fafián Alvarez]

 que sí puede encontrar 'find'. Es un fichero de cabecera de C que tampoco
 encuentra el compilador a pesar de que debería (en teoría) hacerlo pq el
 programa está probado en otro ordenador y sí que compila. Quizá sea por la
 misma razón por la que 'locate' no es capaz de hallar dicho
 fichero. No lo sé. ¿Alguien sabe a qué puede deberse esto?

No creo que tenga que ver. Lo del locate seguramente es porque el 
fichero
no está en su base de datos, me explico, el locate crea una base de datos
con todos los ficheros del sistema semanalmente - si el sistema está
bien configurado -, si la base de datos tiene más de una semana avisa. El
comando que crea o pone al dia la base de datos es dbupdate. Prueba a
correrlo como root y luego mira si encuentra el archivo, seguramente lo
hará. Lo que pasa es que seguramente lo terminas de introducir en el
sistema y la base de datos de locate no se actualizó.
Lo de que no encuentre las librerías suele ser un problema de
configuración con el path, ya que desafortunadamente no existe un claro
acuerdo sobre dónde deben ir las librerías, y quizá lo busque en el lugar
equivocado.


Saludos !


Mi numero de firma de Drivers para Linux es:00056845
pasaros por:http://www.libranet.com/petition.html

Javier Fafián Alvarez: Numero de usuario Linux: 175.004
en un AMD-K6II a 350 con 64 Mb de RAM
Con  Linux Debian Potato (frozen) kernel 2.2.14

Re: locate

[Jaime E. Villate]

Emilio Hernández Martín wrote:
 Tengo un fichero que el comando 'locate' no es capaz de encontrar pero
 que sí puede encontrar 'find'.
 ...¿Alguien sabe a qué puede deberse esto?
Puede ser o porque no existia cuando se hizo updatedb la última vez
(el comando updatedb actualiza la base de datos), o porque no da permiso
de lectura al público.
Jaime Villate

Re: locate

[Correcaminos]

El Mon, May 08, 2000 a las 07:38:35PM +0100, Jaime E. Villate dijo: 
 Emilio Hernández Martín wrote:
  Tengo un fichero que el comando 'locate' no es capaz de encontrar pero
  que sí puede encontrar 'find'.
  ...¿Alguien sabe a qué puede deberse esto?
 Puede ser o porque no existia cuando se hizo updatedb la última vez
 (el comando updatedb actualiza la base de datos), o porque no da permiso
 de lectura al público.

... o porque le hayas añadido un espacio (o cualquier otro caracter
invisible) al final del nombre fichero ...

-- 
=8=
___   _
  / ___|_   _| (_) ___  Grupo de Usuarios de LInux de Canarias
 | |  _| | | | | |/ __| Pasate por nuestro web
 | |_| | |_| | | | (__  http://www.gulic.org/
  \|\__,_|_|_|\___| Clave GPG en las paginas de Gulic
Clave GPG en search.keyserver.net
  Key fingerprint = F734 17F5 3AB6 E1F6 11C4  B498 5B3E  FEDF 90DF
=8=

pgp9i2PbKijbH.pgp
Description: PGP signature

Re: locate

[Jordi Mallach]

On Mon, May 08, 2000 at 07:38:35PM +0100, Jaime E. Villate wrote:
  ...¿Alguien sabe a qué puede deberse esto?
 Puede ser o porque no existia cuando se hizo updatedb la última vez
 (el comando updatedb actualiza la base de datos)

Puedes instalar anacron, si tu ordenador no está encendido normalmente.
Esto hará que la db se te actualice a diario.

-- 
Jordi Mallach Pérez || [EMAIL PROTECTED]   || Rediscovering Freedom,
ka Oskuro in RL-MUD || [EMAIL PROTECTED]|| Using Debian GNU/Linux

http://sindominio.net  GnuPG public information:  pub  1024D/917A225E 
telnet pusa.uv.es 23   73ED 4244 FD43 5886 20AC  2644 2584 94BA 917A 225E


pgprOkz6suKdz.pgp
Description: PGP signature

Re: locate warning . . . ?

[kmself]

On Tue, Mar 28, 2000 at 10:44:12PM -0800, kmself@ix.netcom.com wrote:
 On Tue, Mar 28, 2000 at 02:01:05PM +0200, Joachim Trinkwitz wrote:
  kmself@ix.netcom.com writes:
  
   There have been several reports of similar problems, most of which
   appear to be associated with anacron, an occasional jobs schedular
   similar to cron.
   
   I had the problem myself on two boxes.  Apparently one or more of the
   scripts in /etc/cron.daily was bugging out when run under anacron --
   though I have no clear understanding why this should be, as both anacron
   and cron run run-parts with the same arguments.
  
  I have got the same problem since several days, anacron seems to be
  the trouble maker here too.
  
  Did anyone file a bug report? If not, I would do it, but better if
  someone has a better understanding of the real problem (and a
  workaround, maybe).
 
 Neither 'anacron' nor 'findutils' list any current bug reports which
 match this symptom, according to the bug tracking system:
 http://www.debian.org/Bugs/

Followup to self:

The problem (hung anacron jobs leading to out-of-date whatis (locate)
database) appears to result on my system from a hung logrotate process.
This happens sporadically, not sure why.

-- 
Karsten M. Self (kmself@ix.netcom.com)
What part of Gestalt don't you understand?
http://gestalt-system.sourceforge.net/

Re: locate warning . . . ?

[kmself]

On Tue, Mar 28, 2000 at 02:01:05PM +0200, Joachim Trinkwitz wrote:
 kmself@ix.netcom.com writes:
 
  There have been several reports of similar problems, most of which
  appear to be associated with anacron, an occasional jobs schedular
  similar to cron.
  
  I had the problem myself on two boxes.  Apparently one or more of the
  scripts in /etc/cron.daily was bugging out when run under anacron --
  though I have no clear understanding why this should be, as both anacron
  and cron run run-parts with the same arguments.
 
 I have got the same problem since several days, anacron seems to be
 the trouble maker here too.
 
 Did anyone file a bug report? If not, I would do it, but better if
 someone has a better understanding of the real problem (and a
 workaround, maybe).

Neither 'anacron' nor 'findutils' list any current bug reports which
match this symptom, according to the bug tracking system:
http://www.debian.org/Bugs/

-- 
Karsten M. Self (kmself@ix.netcom.com)
What part of Gestalt don't you understand?
http://gestalt-system.sourceforge.net/

Re: locate warning . . . ?

[Bart Friederichs]

 locate: warning: database `/var/lib/locate/locatedb' is more than 8 days
 old
 Any ideas about what this means?
It means what it says, the database is more than 8 days old. When you do
'updatedb' it indexes your filesystems and puts that info in
/var/lib/locate/locatedb' to speed up the search. You should update that
database every few days to make sure all files are in it.

Bart

Ps
I have my updatedb in crontab, so that i don't have to bother about it. It
updates every monday at 10.

Re: locate warning . . . ?

[Joe Bouchard]

On Mon, Mar 27, 2000 at 03:10:35PM -0600, Bryan Walton wrote:
 Greetings,
   Today, I have noticed that when I do a locate on something, I get
 a warning message that locatedb is more than 8 days old.  See the example:
 Any ideas about what this means?

The program updatedb needs to run regularly to update your locate database.

- Take a look at you /etc/crontab.  Mine shows:
  # m h dom mon dow user  command
  40 6* * *   rootrun-parts --report /etc/cron.daily
  If you look in /etc/cron.daily directory, you will see a find
  script, and if you look in that, you will see it calls updatedb.  In
  my case it runs at 6:40am every morning (I think that is a non
  standard time that I chose). If my computer isn't powered up at that
  time, it wouldn't run.  Is that your case?

- I have a potato machine I upgraded from slink a few months ago.  It
  seemed like there was a typo in one of the scripts (or something like
  that) which caused this problem as you described, even if the machine
  was left on.  I think the problem got fixed when I did an apt-get
  upgrade.  I might be wrong about this, it's been a while . . .

- If in doubt, run updatedb as root before doing a locate (like if you
  just installed new packages and want to do a search).

-- 

Thank you,
Joe Bouchard

Powered by Debian GNU/Linux

Re: locate warning . . . ?

[Wayne Topa]

Subject: locate warning . . . ?
Date: Mon, Mar 27, 2000 at 03:10:35PM -0600

In reply to:Bryan Walton

Quoting Bryan Walton([EMAIL PROTECTED]):
| Greetings,
|  Today, I have noticed that when I do a locate on something, I get
| a warning message that locatedb is more than 8 days old.  See the example:
| --cut--
| 
| work:/home/walton# locate xf86config
| locate: warning: database `/var/lib/locate/locatedb' is more than 8 days 
| old
| /usr/share/alien/patches/xf86config-glibc_1.0.0.i386-3.diff.gz
| /usr/X11R6/bin/xf86config
| /usr/X11R6/man/man1/xf86config.1x.gz
| 
| --cut--
| 
| Any ideas about what this means?
| 
| Thanks,
| Bryan Walton

Umm, that the locate database has not been updated in 8 days.

read  man updatedb

then try this

updatedb --prunepaths='/tmp /proc /cdrom /mnt /var/spool'  /dev/null 21

HTH


-- 
Computers are not intelligent. They only think they are.
___

Re: locate warning . . . ?

[kmself]

There have been several reports of similar problems, most of which
appear to be associated with anacron, an occasional jobs schedular
similar to cron.

I had the problem myself on two boxes.  Apparently one or more of the
scripts in /etc/cron.daily was bugging out when run under anacron --
though I have no clear understanding why this should be, as both anacron
and cron run run-parts with the same arguments.

Other symptoms you may want to check for are one or more hanging anacron
processes, and/or zombie processes related to your /etc/cron.daily
scripts.

The fix in my case was to remove the anacron package, as both the
affected systems are up 24/7.  While cron will run the scripts in
/etc/cron.(daily|weekly|monthly), you may miss a cycle if your system is
down when the job would normally have run.

On Mon, Mar 27, 2000 at 03:10:35PM -0600, Bryan Walton wrote:
 Greetings,
   Today, I have noticed that when I do a locate on something, I get
 a warning message that locatedb is more than 8 days old.  See the example:
 --cut--
 
 work:/home/walton# locate xf86config
 locate: warning: database `/var/lib/locate/locatedb' is more than 8 days 
 old
 /usr/share/alien/patches/xf86config-glibc_1.0.0.i386-3.diff.gz
 /usr/X11R6/bin/xf86config
 /usr/X11R6/man/man1/xf86config.1x.gz
 
 --cut--
 
 Any ideas about what this means?
 
 Thanks,
 Bryan Walton
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null
 

-- 
Karsten M. Self (kmself@ix.netcom.com)
What part of Gestalt don't you understand?
http://gestalt-system.sourceforge.net/

Re: locate warning . . . ?

[Steve Mayer]

Bryan,

  The error means that updatedb has not been run through your
cron scripts as it should have.  su to the root account and try
running /etc/cron.daily/find and see if you get any errors.

Steve

Bryan Walton wrote:
 
 Greetings,
 Today, I have noticed that when I do a locate on something, I get
 a warning message that locatedb is more than 8 days old.  See the example:
 --cut--
 
 work:/home/walton# locate xf86config
 locate: warning: database `/var/lib/locate/locatedb' is more than 8 days
 old
 /usr/share/alien/patches/xf86config-glibc_1.0.0.i386-3.diff.gz
 /usr/X11R6/bin/xf86config
 /usr/X11R6/man/man1/xf86config.1x.gz
 
 --cut--
 
 Any ideas about what this means?
 
 Thanks,
 Bryan Walton
 
 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

Re: locate warning . . . ?

[Kevin Dalley]

Which version of findutils do you have installed?  findutils-4.1-40 is
the preferred version.  If you are using certain older versions,
updatedb will not run on a daily basis.

Usually, /etc/cron.daily/find is run every day, which updates locatedb.

Bryan Walton [EMAIL PROTECTED] writes:

 Greetings,
   Today, I have noticed that when I do a locate on something, I get
 a warning message that locatedb is more than 8 days old.  See the example:
 --cut--
 
 work:/home/walton# locate xf86config
 locate: warning: database `/var/lib/locate/locatedb' is more than 8 days 
 old
 /usr/share/alien/patches/xf86config-glibc_1.0.0.i386-3.diff.gz
 /usr/X11R6/bin/xf86config
 /usr/X11R6/man/man1/xf86config.1x.gz
 
 --cut--
 
 Any ideas about what this means?
 
 Thanks,
 Bryan Walton
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

-- 
Kevin Dalley
[EMAIL PROTECTED]

Re: locate warning . . . ?

[Joachim Trinkwitz]

kmself@ix.netcom.com writes:

 There have been several reports of similar problems, most of which
 appear to be associated with anacron, an occasional jobs schedular
 similar to cron.
 
 I had the problem myself on two boxes.  Apparently one or more of the
 scripts in /etc/cron.daily was bugging out when run under anacron --
 though I have no clear understanding why this should be, as both anacron
 and cron run run-parts with the same arguments.

I have got the same problem since several days, anacron seems to be
the trouble maker here too.

Did anyone file a bug report? If not, I would do it, but better if
someone has a better understanding of the real problem (and a
workaround, maybe).

Greetings,
joachim

Re: Locate question

[Kevin Dalley]

Yes, there was a bad NMU to findutils just before the freeze.  4.1-37
fixes this problem.

John Bagdanoff [EMAIL PROTECTED] writes:

 I've noticed this the last few days with both slink to potato upgrade and a 
 fresh
 potato install on another drive.  The problem looks like the latest findutils
 package.  I downgraded to the slink findutils which fixed the problem.
 
 John
 
 Svante Signell wrote:
 
  Hello,
 
  Sometime during updates from slink to potato the locate database is
  not updated any longer. Anacron is running after a reboot, but the
  updatedb does not locate recent files. Can somebody enlightenment me
  how things are workingtogether:
  find, locate, update, updatedb, anacron and cron.


-- 
Kevin Dalley
[EMAIL PROTECTED]

Re: Locate question

[John Bagdanoff]

I've noticed this the last few days with both slink to potato upgrade and a 
fresh
potato install on another drive.  The problem looks like the latest findutils
package.  I downgraded to the slink findutils which fixed the problem.

John

Svante Signell wrote:

 Hello,

 Sometime during updates from slink to potato the locate database is
 not updated any longer. Anacron is running after a reboot, but the
 updatedb does not locate recent files. Can somebody enlightenment me
 how things are workingtogether:
 find, locate, update, updatedb, anacron and cron.

 Svante Signell

 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

Re: Locate question

[Paul J. Keenan]

On Mon, Jan 24, 2000 at 10:13:42PM +0100, Svante Signell wrote:
 Hello,
 
 Sometime during updates from slink to potato the locate database is
 not updated any longer. Anacron is running after a reboot, but the
 updatedb does not locate recent files. Can somebody enlightenment me
 how things are workingtogether:
 find, locate, update, updatedb, anacron and cron.
 
 Svante Signell

cron runs all entries in /etc/cron.d, which includes
/etc/cron.d/anacron.  This contains log entries which frequently invoke
anacron.

anacron uses timestamp information from /var/spool/anacron/* to decide
when to run the daily, weekly and monthly jobs, which are stored in
/etc/cron.(daily|weekly|monthly).

/etc/cron.daily/find is run each day by anacron by virtue of being
in the /etc/cron.d directory.  It contains the updatedb command.

locate uses the information produced by updatedb for fast file
searches.

A find command can be used for the same task as locate, but slower.
Find has a million and one options for specialised searches, though.

update is a command to periodically flush filesystem buffers, so I
think you might be onto a red herring here ... :-)

HTH.

-- 
Regards,
Paul

Re: locate

[Martin Bialasinski]

herbert betz [EMAIL PROTECTED] writes:

 as a linux newbie I don't know how to fix a problem I have using LOCATE.
 It worked allright, when I installed it, but after a while UPDATEDB and
 LOCATE didn't seem to do anything, when I invoked them (except giving back
 the prompt without any message). Manpage or reinstalling locate didn't help 
 either. I'm
 using SuSE Linux 4.4 on a pentium120. I'm running locate mostly as root.

I am sure you will get all help you need in a mailinglist about SUSE
Linux. Check out www.suse.com for their lists.

I believe hardly anyone here knows where SUSE stores its stuff and what
customisation they did. Maybe there is a bug in the specific package you
use. The guys at SUSE will tell you. 

Ciao,
Martin

BTW: Debian is a great Linux distribution. Maybe you want to switch?


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Locate

[Kevin Dalley]

Pete Poff [EMAIL PROTECTED] writes:

 
 Hi,
   when I use locate I get an error.  This is what I get if I type 
 like locate what ever.  Like locate new.stuff.  I get locate: 
 /var/lib/locate/locatedb: No suck file or directory.  Can anyone tell me 
 why?

Another possibility is that you are using an old, buggy version of
findutils.  findutils-4.1-20 is the best version, which is currently
in frozen.  I introduced some bugs in the early versions of the
current stable release of findutils.




-- 
Kevin Dalley
[EMAIL PROTECTED]

Re: Locate

[Rob Browning]

Pete Poff [EMAIL PROTECTED] writes:

   when I use locate I get an error.  This is what I get if I type 
 like locate what ever.  Like locate new.stuff.  I get locate: 
 /var/lib/locate/locatedb: No suck file or directory.  Can anyone tell me 
 why?  And is there a command to see how much disk space I have left?

Chances are you are experiencing a bug in an older cron package.
There was a version which would not set up cron to run automatically
at boot time.  You can get it cron started with

 /etc/init.d/cron start

as root.  And you can fix the problem permanently by upgrading your
cron package.

-- 
Rob

Re: Locate

[Giuliano Procida]

Rob Browning [EMAIL PROTECTED] wrote:

 Pete Poff [EMAIL PROTECTED] writes:
 
when I use locate I get an error.  This is what I get if I type
  like locate what ever.  Like locate new.stuff.  I get locate:
  /var/lib/locate/locatedb: No suck file or directory.  Can anyone tell me
  why?  And is there a command to see how much disk space I have left?
 
 Chances are you are experiencing a bug in an older cron package.
 There was a version which would not set up cron to run automatically
 at boot time.  You can get it cron started with
 
  /etc/init.d/cron start
 
 as root.  And you can fix the problem permanently by upgrading your
 cron package.

However, this doesn't explain why there is no locatedb at all;
whenever /etc/init.d/boot runs to completion it looks for an
executable file /sbin/setup.sh and it is this script that is supposed
to run updatedb for the first time and then delete itself.

The current install disks for Debian installation have a bug which
leaves the setup.sh script unexecutable; you may find it still exists
on your system with mode 0.

Does this explain anything in your (Pete's) case?

Giuliano Procida.

Re: Locate

[John Ireland]

  when I use locate I get an error.  This is what I get if I type 
  like locate what ever.  Like locate new.stuff.  I get locate: 
  /var/lib/locate/locatedb: No suck file or directory.  Can anyone tell me 
  why?  And is there a command to see how much disk space I have left?
  
  Thanks,
 Hi Pete
   not sure about the locate cmd but to see you current disk usage
 use the df command. look at man df and also man locate.

Locate searches through a database of files stored on your machine. You 
can create or update this file at any time as root, by running 
'updatedb'. This ensures that the db exists and is up to date.

John

-
John Ireland JCR Computer Rep
Jesus College, OX1 3DW[EMAIL PROTECTED]

(01865) 511290http://www.jesus.ox.ac.uk/~jireland

`It is a wise man who knows when to quit.'   (finger [EMAIL PROTECTED])

Re: Locate

[System Account]

On Fri, 7 Mar 1997, Pete Poff wrote:

 Hi,
   when I use locate I get an error.  This is what I get if I type 
 like locate what ever.  Like locate new.stuff.  I get locate: 
 /var/lib/locate/locatedb: No suck file or directory.  Can anyone tell me 
 why?  And is there a command to see how much disk space I have left?
 
 Thanks,
Hi Pete
not sure about the locate cmd but to see you current disk usage
use the df command. look at man df and also man locate.

-Rob

Re: Locate

[Thought]

Try running updatedb to fix your locate problem

df will tell you about your disk space

On Fri, 7 Mar 1997, Pete Poff wrote:

 Hi,
   when I use locate I get an error.  This is what I get if I type 
 like locate what ever.  Like locate new.stuff.  I get locate: 
 /var/lib/locate/locatedb: No suck file or directory.  Can anyone tell me 
 why?  And is there a command to see how much disk space I have left?
 
 Thanks,
  Pete Poff---AKA---BlackJack
Personal E-Mail Address: [EMAIL PROTECTED]
  Kyron E-Mail Address:[EMAIL PROTECTED]
Kyron address: telnet.cyberconinc.com 4000
 
 

Re: Locate

[Heikki Vatiainen]

If you check /etc/crontab you'll notice that there's a line that does 
something like 'run-parts /etc/cron.daily'. /etc/cron.daily has among others a 
file called 'find' that includes the commands to update the locatedb.

Like the name implies, files in /etc/cron.daily are run once a day, in my case 
at 6:42 am. Cron, crontab, updatedb, run-parts etc. have all manpages that 
have more info about them.

If you want your locatedb updated now, just run /etc/cron.daily/find as root 
and wait a little. I guess your locate database was never initially built.

Pete Poff wrote:
[cut]
 like locate what ever.  Like locate new.stuff.  I get locate: 
 /var/lib/locate/locatedb: No suck file or directory.  Can anyone tell me 
 why?  And is there a command to see how much disk space I have left?

// Heikki
-- 
Heikki Vatiainen  * [EMAIL PROTECTED]
Tampere University of Technology  * Tampere, Finland

Re: Locate

[David Puryear]

Hi, 

On 08-Mar-97 Heikki Vatiainen wrote:
If you check /etc/crontab you'll notice that there's a line that does 
something like 'run-parts /etc/cron.daily'. /etc/cron.daily has among others a 
file called 'find' that includes the commands to update the locatedb.

Like the name implies, files in /etc/cron.daily are run once a day, in my case 
at 6:42 am. Cron, crontab, updatedb, run-parts etc. have all manpages that 
have more info about them.

If you want your locatedb updated now, just run /etc/cron.daily/find as root 
and wait a little. I guess your locate database was never initially built.

Shouldn't this be automagically done when base is installed? I seems to get same
error. 

Thanks,
David

Pete Poff wrote:
[cut]
 like locate what ever.  Like locate new.stuff.  I get locate: 
 /var/lib/locate/locatedb: No suck file or directory.  Can anyone tell 
 why?  And is there a command to see how much disk space I have left?