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
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’:
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
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.
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"
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
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
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:
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
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
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
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
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
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
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:
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
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.
> > 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
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
чт, 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
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.
> >
>
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
чт, 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 .
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,
--
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
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
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
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
>
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
* 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
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
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
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
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.
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
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
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
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()_()
`-
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 ?
--
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
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...
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
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
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,
et après, sous root, taper updatedb
pour mettre la base de données à jour.
man locate est aussi ton ami.
A+
Olivier
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
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
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
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.
--
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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
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
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
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:
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
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
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
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
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).
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
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
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?
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,
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
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
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
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
96 matches
Mail list logo
