On Tuesday, 01 April, 2014 09:08:47 debian-user-digest-
requ...@lists.debian.org wrote:
In the same mail an observation was made. It implied that the file
cron-spamassassin-rules was put in /etc/cron.daily by you and not by a
Debian package. Do you have a response to that too?
On Tue 01 Apr 2014 at 12:47:32 +0300, David Baron wrote:
Have removed it. The whole spamassassin thing seems broken right now.
How do I tell if locate script actually had run on today's startup?
I give up:
ls -l /var/lib/mlocate/mlocate.db
--
To UNSUBSCRIBE, email to
More ...
There is a locate script in /etc/cron.daily which should be run as a matter or
daily anacron course. Has not been. No entry in syslog. Syslog has not been
daily-logrotated during this period either.
The working part of the locate script can be run manually.
--
To UNSUBSCRIBE, email
On Mon 31 Mar 2014 at 13:22:04 +0300, David Baron wrote:
More ...
In another mail you were asked a single question. Do you have a response
to that question?
In the same mail an observation was made. It implied that the file
cron-spamassassin-rules was put in /etc/cron.daily by you and not by a
In another mail you were asked a single question. Do you have a response
to that question?
Stated that machine does not run 24h
In the same mail an observation was made. It implied that the file
cron-spamassassin-rules was put in /etc/cron.daily by you and not by a
Debian package. Do you
On Mon 31 Mar 2014 at 23:07:24 +0300, David Baron wrote:
In the same mail an observation was made. It implied that the file
cron-spamassassin-rules was put in /etc/cron.daily by you and not by a
Debian package. Do you have a response to that too?
Here is the contents
#!/bin/sh -e
#
On Mon, Mar 31, 2014 at 10:48:49PM +0100, Brian wrote:
On Mon 31 Mar 2014 at 23:07:24 +0300, David Baron wrote:
In the same mail an observation was made. It implied that the file
cron-spamassassin-rules was put in /etc/cron.daily by you and not by a
Debian package. Do you have a
I guess, for almost three weeks now.
Running Sid on 686 box.
Anybody know of this?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/34925084.lMkecSoAQs@dovidhalevi
On Sun 30 Mar 2014 at 10:18:36 +0300, David Baron wrote:
I guess, for almost three weeks now.
Running Sid on 686 box.
Anybody know of this?
Is the machine on 24 hours a day? Please post the output of
ps ax | grep cron
and
dpkg -l | grep cron
--
To UNSUBSCRIBE, email to
On Sunday, 30 March, 2014 11:41:10 debian-user-digest-requ...@lists.debian.org
wrote:
I guess, for almost three weeks now.
Running Sid on 686 box.
Anybody know of this?
Is the machine on 24 hours a day?
No
Please post the output of
ps ax | grep cron
4230 ?Ss
On Sun 30 Mar 2014 at 14:58:17 +0300, David Baron wrote:
On Sunday, 30 March, 2014 11:41:10
debian-user-digest-requ...@lists.debian.org
wrote:
[Is it my fate to be erased from Debian history? I suppose I could get
used in time to being re-named. :) ]
Is the machine on 24 hours a day?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Victor Munoz wrote:
It worked. All missing files are there now.
At first, this was a mystery, but now I understand why. updatedb is
not run as root, but as 'nobody', as set in /etc/updatedb.conf, so
the sequence
$ . /etc/updatedb.conf;
Hello. Today I found a very strange problem. Some files seem to be
missing from locatedb database.
It all started with one particular file I wanted to find. But 'locate
word' didn't find the file I was looking for. I went to the
directory it was supposed to be, and there it was!
I have a cron
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Victor Munoz wrote:
Hello. Today I found a very strange problem. Some files seem to be
missing from locatedb database.
[snip]
I don't understand. Does any?
Try running 'updatedb' as root manually and check if this helps.
Johannes
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/27/07 12:38, Victor Munoz wrote:
Hello. Today I found a very strange problem. Some files seem to be
missing from locatedb database.
It all started with one particular file I wanted to find. But 'locate
word' didn't find the file I
On Thu, Sep 27, 2007 at 03:21:32PM -0400, Victor Munoz wrote:
On Thu, Sep 27, 2007 at 01:43:14PM -0500, Ron Johnson wrote:
Some files in the original problematic directory have permissions
-rw--- (does updatedb respect this), but the file I was looking
for in the first place has
On Thu, Sep 27, 2007 at 01:43:14PM -0500, Ron Johnson wrote:
Some files in the original problematic directory have permissions
-rw--- (does updatedb respect this), but the file I was looking
for in the first place has read permissions for all.
I don't understand. Does any?
On Thu, Sep 27, 2007 at 12:26:43PM -0700, Andrew Sackville-West wrote:
what are the permissions on the parent directories? that might be more
relevant.
drwxr-xr-x in all cases.
Victor
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On Thu, Sep 27, 2007 at 08:23:14PM +0200, Johannes Wiedersich wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Victor Munoz wrote:
Hello. Today I found a very strange problem. Some files seem to be
missing from locatedb database.
[snip]
I don't understand. Does any?
Try
On Thu, Sep 27, 2007 at 03:31:23PM -0400, Victor Munoz wrote:
On Thu, Sep 27, 2007 at 12:26:43PM -0700, Andrew Sackville-West wrote:
what are the permissions on the parent directories? that might be more
relevant.
drwxr-xr-x in all cases.
Wrong. One had permissions drwxr-xr-- as I
On 09/27/2007 02:21 PM, Victor Munoz wrote:
On Thu, Sep 27, 2007 at 01:43:14PM -0500, Ron Johnson wrote:
Some files in the original problematic directory have permissions
-rw--- (does updatedb respect this), but the file I was looking
for in the first place has read permissions for all.
I
On Thu, Sep 27, 2007 at 03:31:23PM -0400, Victor Munoz wrote:
On Thu, Sep 27, 2007 at 12:26:43PM -0700, Andrew Sackville-West wrote:
what are the permissions on the parent directories? that might be more
relevant.
drwxr-xr-x in all cases.
are these directories nfs mounts by any
On Thu, Sep 27, 2007 at 02:53:18PM -0500, Mumia W.. wrote:
Check /etc/updatedb.conf and the LOCALUSER variable. LOCALUSER is set to
'nobody' by default, and 'nobody' has no ability to view directories
with -rwx-- permissions.
That was the problem, indeed. Thanks,
Victor
--
To
/var/cache/locate/locatedb is world readable. Is this the correct
default? Can it be made so only certain users have file-level access to
it? (In Redhat there's 'slocate' group and the locate command is setgid
to that group.)
Regards,
dave
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
1489507 Jan 7 06:29 locatedb
lusig1:~#
On Fri, 07 Jan 2005 15:44:46 +0700, David Garamond
[EMAIL PROTECTED] wrote:
/var/cache/locate/locatedb is world readable. Is this the correct
default? Can it be made so only certain users have file-level access to
it? (In Redhat there's 'slocate' group
David Garamond wrote:
/var/cache/locate/locatedb is world readable. Is this the correct
default? Can it be made so only certain users have file-level access to
it? (In Redhat there's 'slocate' group and the locate command is setgid
to that group.)
Sorry, a followup question. I deleted /etc
On Fri, Jan 07, 2005 at 04:33:45PM +0700, David Garamond wrote:
Sorry, a followup question. I deleted /etc/cron.daily/find several days
ago. How do I get it back? Reinstalling the findutils package (using
synaptic) doesn't bring it back.
Do I have to purge and install?
Have you tried
On Fri, Jan 07, 2005 at 04:30:01PM +0700, David Garamond wrote:
I think you think I said 'world writable'? I don't want normal users to
be able to _read_ that file (unless through the locate command, which
will not allow other users' files from being printed).
Ah, a top-post to a message
Jon Dowland wrote:
On Fri, Jan 07, 2005 at 04:30:01PM +0700, David Garamond wrote:
I think you think I said 'world writable'? I don't want normal users to
be able to _read_ that file (unless through the locate command, which
will not allow other users' files from being printed).
Ah, a top-post
Carl Fink wrote:
On Fri, Jan 07, 2005 at 04:33:45PM +0700, David Garamond wrote:
Sorry, a followup question. I deleted /etc/cron.daily/find several days
ago. How do I get it back? Reinstalling the findutils package (using
synaptic) doesn't bring it back.
Do I have to purge and install?
Have you
David Garamond wrote:
Jon Dowland wrote:
Ah, a top-post to a message posted off-list. D-u is getting to be as
readable as work email :-)
Yeah, sorry about the off-list thing. However, I always thought the
proper (polite?) way to reply to a top-post is by another top-post?
I can see the logic in
David Garamond wrote:
Sorry, a followup question. I deleted /etc/cron.daily/find several
days ago. How do I get it back? Reinstalling the findutils package
(using synaptic) doesn't bring it back.
Do I have to purge and install?
[EMAIL PROTECTED]:/home/westk apt-file search /etc/cron.daily/find
On Fri, Jan 07, 2005 at 08:29:55AM -0600, Kent West wrote:
David Garamond wrote:
Sorry, a followup question. I deleted /etc/cron.daily/find several
days ago. How do I get it back? Reinstalling the findutils package
(using synaptic) doesn't bring it back.
Do I have to purge and install?
* David Garamond [EMAIL PROTECTED] [050107 09:44]:
/var/cache/locate/locatedb is world readable. Is this the correct
default? Can it be made so only certain users have file-level access to
it? (In Redhat there's 'slocate' group and the locate command is setgid
to that group.)
Wouldn't
Alexander Schmehl wrote:
* David Garamond [EMAIL PROTECTED] [050107 09:44]:
/var/cache/locate/locatedb is world readable. Is this the correct
default? Can it be made so only certain users have file-level access to
it? (In Redhat there's 'slocate' group and the locate command is setgid
wieder eien Datei suche (meist erst sehr viel später),
ist /var/lib/locate/locatedb wieder quasi leer.
--
cu
Alex
--
PGP key on demand, mailto:[EMAIL PROTECTED] with subject get pgp-key
--
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail
auch wieder. Wenn
ich dann aber wieder eien Datei suche (meist erst sehr viel später),
ist /var/lib/locate/locatedb wieder quasi leer.
Schon mal
find /etc -type f | xargs grep -ils locate
(und updatedb) eingegeben und über das Ergebnis nachgedacht? Nein, ich
habe keine Lösung, aber vielleicht
As I said the first time, updatedb.conf isn't used in casual use of
updatedb. Look at the cron job:
if [ -f /etc/updatedb.conf ]; then
. /etc/updatedb.conf
fi
That '.' means that the contents of updatedb.conf are read and used to
set environment variables. If you were doing this
router:~# locate \* | wc -l
68558
router:~# updatedb
router:~# locate \* | wc -l
91395
Every night, updatedb runs, and updates, removing something like 21000
files from the locatedb. Looking through the cron.daily, i see updatedb
runs as nobody. Is there a particular danger in running
:
Every night, updatedb runs, and updates, removing something like 21000
files from the locatedb. Looking through the cron.daily, i see updatedb
runs as nobody. Is there a particular danger in running this as other
than nobody?
On multi-user-systems, yes.
Imagine files like
waldner:~$ ls -al
On Wed, 18 Jul 2001 13:27:09 EDT, Mike Dresser writes:
Every night, updatedb runs, and updates, removing something like 21000
files from the locatedb. Looking through the cron.daily, i see updatedb
runs as nobody. Is there a particular danger in running this as other
than nobody?
On multi-user
Mike Dresser [EMAIL PROTECTED] wrote:
router:~# locate \* | wc -l
68558
router:~# updatedb
router:~# locate \* | wc -l
91395
Every night, updatedb runs, and updates, removing something like 21000
files from the locatedb.
Perhaps it's ignoring some of the paths and filesystems it's told to
prune
Robert Waldner [EMAIL PROTECTED] writes:
Well, there´s no point in making files only readable by specific users/
groups if locate would locate them just nicely for everyone ;-)
Of course there is! They may be able to locate them, but they still
can't _read_ them.
Now, there may be cases
On Wed, 18 Jul 2001 at 15:19:06 -0400, Mike Dresser wrote:
[Please do *not* cc me on list mail. I read the list. Thanks.]
On Wed, 18 Jul 2001, Colin Watson wrote:
Perhaps it's ignoring some of the paths and filesystems it's told to
prune in /etc/updatedb.conf? Those are only noticed by the
On Wed, 18 Jul 2001, Colin Watson wrote:
Mike Dresser [EMAIL PROTECTED] wrote:
router:~# locate \* | wc -l
68558
router:~# updatedb
router:~# locate \* | wc -l
91395
Every night, updatedb runs, and updates, removing something like 21000
files from the locatedb.
Perhaps it's ignoring
On Wed, Jul 18, 2001 at 01:27:09PM -0400, Mike Dresser wrote:
router:~# locate \* | wc -l
68558
router:~# updatedb
router:~# locate \* | wc -l
91395
Every night, updatedb runs, and updates, removing something like 21000
files from the locatedb. Looking through the cron.daily, i see
Also, could anyone tell me how to activate the locatedb so I can use locate?
Thanx.
XsX
don't turn your computer off at night.
(the locatedb is rebuilt in a daily cron job run at 06:25)
I am getting am mail every night at this time and I never knew what it was
for. What
Stephan Kulka [EMAIL PROTECTED] writes:
What is locatedb or locate? Where should I start reading?
Have a look at the manpages of locate and locatedb. locatedb is the
database created by updatedb and used by locate. it holds a list of
filenames, then you can quickly search with locate for files
48 matches
Mail list logo
