bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: locate(1) man page hard to understand, please rewrite


From: Stepan Kasal
Subject: Re: locate(1) man page hard to understand, please rewrite
Date: Mon, 8 Jul 2002 11:35:54 +0000 (UTC)
User-agent: slrn/0.9.6.2 (Linux)

Hallo,

On 07 Jul 2002 00:26:48 -0400, Paul D. Smith <address@hidden> wrote:
A few corrections:

>   $ locate /tmp

will match every line containing substring "/tmp" since it contains no
metacharacter.  Thus it's equivalent to

>   $ locate '*/tmp*'

What you need is

    $ locate '*/tmp'

which is equivalent to grep pattern '^.*/tmp$' or '/tmp$'.

Well, I was able to catch this from the parts of the manpage you have cited.
You may try to re-write it, if you want, but be careful that your version
still accurately describes the behaviour of locate.

When you perform the above command, you may get

/home/tmp
/usr/local/tmp

and similar, and not get the obvious ones: "/tmp", "/var/tmp" and so on.

The reason is that the updatedb command is often configured to omit the
most obvious useless directories, like /tmp and /mnt .
Search your cron configuration for details.

Hope this helps,
        Stepan Kasal





reply via email to

[Prev in Thread] Current Thread [Next in Thread]