Re: Locatedb not Updating
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? Here is the contents #!/bin/sh -e # spamd -4 # do spamassassin rules update echo Updating Spamassassin rules... sa-update sleep 30 #echo Restarting Spamassassin daemon... /etc/init.d/spamassassin restart echo Done. #echo Restarting Fetchmail daemon... /etc/init.d/fetchmail restart echo Done. We'll now assume this file is not from a Debian package and that anacron comes to a halt when running it because it is defective. Repairing it may be the subject of another thread. Meanwhile: Please follow the detailed instructions you have been given. Moving cron-spamassassin-rules out of cron.daily should allow anacron to process all the other files in the directory. Once you have solved the problem posed in the subject of this thread you can go on to dealing with the wayward file. 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? Forgive me if I'm off base here, but what if the sa-update background job takes longer than 30(s ?) hy not just run 'sa-update' in the foreground ditch the 'sleep 30', you might even save a bit of time in the long run (your way it'll sleep 30 regardless how long 'sa-update' takes. This was originally in rc.local, foreground as you suggested. It did hang, hanging following rc.local items. Why is was taken out of there and placed as a cron.daily job. Since there is a problem with spamassassin right now, just skipping this is best until that is resolved. -- 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/2478686.lT3kdaoTX3@dovidhalevi
Re: Locatedb not Updating
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 debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/01042014184321.1b26cc081...@desktop.copernicus.demon.co.uk
Re: Locatedb not Updating
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 to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2576971.3LGLdeRNPK@dovidhalevi
Re: Locatedb not Updating
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 Debian package. Do you have a response to that too? We are now reduced to guessing that cron-spamassassin-rules is not a Debian file and it is the problem. 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. There is an *mlocate* script in /etc/cron.daily. 1. Delete /var/spool/anacron.daily. 2. Move all the files out of /etc/cron.daily apart from 0anacron and mlocate. 3. Run '/usr/sbin/anacron -s'. 4. Does 'ps ax | grep cron' have '/usr/sbin/anacron -s' in its output and does syslog report that anacron was started? 5. 5 minutes later does /var/spool/anacron.daily exist and has syslog been updated to reflect that? Has '/usr/sbin/anacron -s' disappeared from the output of 'ps ax'? 6. Rename cron-spamassassin-rules to spamassassin-rules and add it to /etc/cron.daily. Repeat 1-5. An additional question: are the time data for /var/lib/mlocate/mlocate.db altered? 7. Kill any unwanted processes and repeat 1-6 after renaming spamassassin-rules to cron-spamassassin-rules. The working part of the locate script can be run manually. -- 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/20140331123722.gh3...@copernicus.demon.co.uk
Re: Locatedb not Updating
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 have a response to that too? Here is the contents #!/bin/sh -e # spamd -4 # do spamassassin rules update echo Updating Spamassassin rules... sa-update sleep 30 #echo Restarting Spamassassin daemon... /etc/init.d/spamassassin restart echo Done. #echo Restarting Fetchmail daemon... /etc/init.d/fetchmail restart echo Done. There was apparently lacking regular update of these rules. : I am pretty sure I edited that file (first line) from somewhere but to not recall placing it here date with which it is marked. Content was formerly in my rc.local . I have moved it out, see what happens. Where would correct Debian practice so assure timely update of these rules? There is has been a recurring error (reason from the spamd 4), previously sited here. -- 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/2759761.mWRJ0WMN66@dovidhalevi
Re: Locatedb not Updating
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 # spamd -4 # do spamassassin rules update echo Updating Spamassassin rules... sa-update sleep 30 #echo Restarting Spamassassin daemon... /etc/init.d/spamassassin restart echo Done. #echo Restarting Fetchmail daemon... /etc/init.d/fetchmail restart echo Done. We'll now assume this file is not from a Debian package and that anacron comes to a halt when running it because it is defective. Repairing it may be the subject of another thread. Meanwhile: Please follow the detailed instructions you have been given. Moving cron-spamassassin-rules out of cron.daily should allow anacron to process all the other files in the directory. Once you have solved the problem posed in the subject of this thread you can go on to dealing with the wayward file. -- 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/20140331214849.gk3...@copernicus.demon.co.uk
Re: Locatedb not Updating
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 response to that too? Here is the contents #!/bin/sh -e # spamd -4 # do spamassassin rules update echo Updating Spamassassin rules... sa-update sleep 30 #echo Restarting Spamassassin daemon... /etc/init.d/spamassassin restart Forgive me if I'm off base here, but what if the sa-update background job takes longer than 30(s ?) Why not just run 'sa-update' in the foreground ditch the 'sleep 30', you might even save a bit of time in the long run (your way it'll sleep 30 regardless how long 'sa-update' takes. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- 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/20140401014140.GB25733@tal
Locatedb not Updating
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
Re: Locatedb not Updating
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 debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/30032014104925.0b996e194...@desktop.copernicus.demon.co.uk
Re: Locatedb not Updating
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 0:00 /usr/sbin/anacron -s 5417 ?Ss 0:00 /usr/sbin/cron 16281 ?SN 0:00 run-parts --report /etc/cron.daily 27066 ?SN 0:00 /bin/sh -e /etc/cron.daily/cron-spamassassin-rules 30213 pts/1S+ 0:00 grep cron and dpkg -l | grep cron ii anacron 2.3-20 i386 cron-like program that doesn't go by time ii cron3.0pl1-124 i386 process scheduling daemon ii cron-apt0.9.2 all automatic update of packages using apt-get ii kcron 4:4.11.3-1 all program scheduler frontend - transitional package ii kde-config-cron 4:4.11.3-1 i386 program scheduler frontend -- 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/2433164.5CIMylIYZm@dovidhalevi
Re: Locatedb not Updating
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? No Ok, anacron deals with updating the database then. Please post the output of ps ax | grep cron 4230 ?Ss 0:00 /usr/sbin/anacron -s 5417 ?Ss 0:00 /usr/sbin/cron 16281 ?SN 0:00 run-parts --report /etc/cron.daily 27066 ?SN 0:00 /bin/sh -e /etc/cron.daily/cron-spamassassin-rules 30213 pts/1S+ 0:00 grep cron The output is still as you report above? anacron's activities are reported in /var/log/syslog; it must be worth a look there. Also, kill the processes (apart from cron) and see what happens with /usr/sbin/anacron -s run from the command line. Observation: cron-spamassassin-rules does not appear to be a file which is in Debian. It also has the distinction of producing only one result when seached for with cron-spamassassin-rules on Google. Guess where from. :) -- 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/20140330134401.gf3...@copernicus.demon.co.uk
Re: Missing files in locatedb
-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; updatedb yields a lot of Permission denied messages, unlike $ updatedb. And I was wrong when I replied to another post in this thread, saying that all directories had permissions drwxr-xr-x. ~/textos/fisica had drwxr-xr--, and that was it. So it's all working now, and much better, I understand :-) Thanks for the help. I use package 'slocate' instead of 'locate': /--- $ aptitude show slocate Package: slocate [snip] Description: Secure replacement of findutil's locate This locate can index all files on your system, but only files and directories which the invoking user has access to will be displayed. Note: If your computer is not up 24/7 you should consider installing anacron since the database is only updated once a night. \--- Usage is like for locate, ie. I type locate, but it will execute slocate. HTH, Johannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/KQjC1NzPRl9qEURAmNNAJ994vsY6IKqt5BFQtHVjs0Mp4+gUACfTCEk BWaMziTDCLv4q9cxMNuP4Us= =9tLN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Missing files in locatedb
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 job to updatedb every night. In fact: $ ls -l /var/cache/locate/ total 7020 -rw-r--r-- 1 root root 7173582 2007-09-27 06:26 locatedb So it seems to be in order. The file I wanted was created in August. So? In fact, none the files in this directory is in the database! In case you're curious, the directory is named ~/textos/fisica/departamento_fisica/departamento In /etc/updatedb.conf, there is the following line: PRUNEPATHS=/tmp /usr/tmp /var/tmp /afs /amd /alex /var/spool /sfs /media So I don't think updatedb should omit this directory. In fact, none of the files in any subdirectory of ~/textos/fisica/departamento_fisica/ is indexed! I've made some random search of files in other directories, and they seem indexed. In fact files in ~/textos itself are indexed. 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? Regards, Victor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Missing files in locatedb
-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 PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+/USC1NzPRl9qEURAkN3AJ9pDW/DYuwggs803MvgiI9/uDv/wwCfXxEL 1eCAPBxlTPzeZ4WQvEwT2pI= =RoV2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Missing files in locatedb
-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 was looking for. I went to the directory it was supposed to be, and there it was! I have a cron job to updatedb every night. In fact: $ ls -l /var/cache/locate/ total 7020 -rw-r--r-- 1 root root 7173582 2007-09-27 06:26 locatedb So it seems to be in order. The file I wanted was created in August. So? In fact, none the files in this directory is in the database! In case you're curious, the directory is named ~/textos/fisica/departamento_fisica/departamento In /etc/updatedb.conf, there is the following line: PRUNEPATHS=/tmp /usr/tmp /var/tmp /afs /amd /alex /var/spool /sfs /media So I don't think updatedb should omit this directory. In fact, none of the files in any subdirectory of ~/textos/fisica/departamento_fisica/ is indexed! I've made some random search of files in other directories, and they seem indexed. In fact files in ~/textos itself are indexed. 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? When were these files created? - -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+/nCS9HxQb37XmcRAqp0AKCjY7VDWXovc/lUiWeiTKFRp2iJvwCePucv wleP/20aTOv5HzhdVisMDpw= =TOSw -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Missing files in locatedb
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 read permissions for all. I don't understand. Does any? When were these files created? There are 7 files with -rw--- permission, last modification times between 2003-10-16 and 2007-06-11, and 9 files with -rw-r--r-- permissions, last modification times between 2007-05-02 and 2007-08-29. Anyway, other directories which don't seem to be indexed either have files with timestamps in various ranges, I don't see any correlation. what are the permissions on the parent directories? that might be more relevant. A signature.asc Description: Digital signature
Re: Missing files in locatedb
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? When were these files created? There are 7 files with -rw--- permission, last modification times between 2003-10-16 and 2007-06-11, and 9 files with -rw-r--r-- permissions, last modification times between 2007-05-02 and 2007-08-29. Anyway, other directories which don't seem to be indexed either have files with timestamps in various ranges, I don't see any correlation. Victor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Missing files in locatedb
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 PROTECTED]
Re: Missing files in locatedb
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 running 'updatedb' as root manually and check if this helps. 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; updatedb yields a lot of Permission denied messages, unlike $ updatedb. And I was wrong when I replied to another post in this thread, saying that all directories had permissions drwxr-xr-x. ~/textos/fisica had drwxr-xr--, and that was it. So it's all working now, and much better, I understand :-) Thanks for the help. Victor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Missing files in locatedb
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 mention in other post, and that's why it failed. Thanks, Victor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Missing files in locatedb
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 don't understand. Does any? When were these files created? There are 7 files with -rw--- permission, last modification times between 2003-10-16 and 2007-06-11, and 9 files with -rw-r--r-- permissions, last modification times between 2007-05-02 and 2007-08-29. Anyway, other directories which don't seem to be indexed either have files with timestamps in various ranges, I don't see any correlation. Victor 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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Missing files in locatedb
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 chance? that's all I can think of, as they are excluded by default. A signature.asc Description: Digital signature
Re: Missing files in locatedb
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 UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
locatedb is world readable
/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] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locatedb is world readable
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). Regards, dave Rem wrote: lusig1:~# ls -l /var/cache/locate/ total 1460 -rw-r--r-- 1 root root 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 and the locate command is setgid to that group.) Regards, dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locatedb is world readable
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/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? Regards, dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locatedb is world readable
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 dpkg-reconfigure findutils? -- Carl Fink [EMAIL PROTECTED] Jabootu's Minister of Proofreading http://www.jabootu.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locatedb is world readable
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 posted off-list. D-u is getting to be as readable as work email :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
OT: Replying to top-post (Re: locatedb is world readable)
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 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? Otherwise, it will be confusing to see something like this: REPLY3_TOPPOST REPLY1_TOPPOST ORIG REPLY2 Regards, dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locatedb is world readable
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 tried dpkg-reconfigure findutils? Yup, tried that but no luck. Btw, the /etc/cron.daily/find was never modified. Regards, dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OT: Replying to top-post (Re: locatedb is world readable)
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 that; however, my usual MO is to fix the top-posting in my reply; it takes more work on my part, but I'd rather it be right. But that's just me. (I also remove CC:s, unless they've been specifically asked for. After all, most everyone on this list, reads the list; no need for them to get two copies of a message.) -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locatedb is world readable
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 findutils: etc/cron.daily/find findutils: etc/cron.daily/find Since you've already reinstalled findutils and that didn't do it, then I'd say, Yep. Try purging and installing. I guess since this file is in /etc, it's considered a configuration file and therefore doesn't get replaced on a plain reinstall. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locatedb is world readable
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? [EMAIL PROTECTED]:/home/westk apt-file search /etc/cron.daily/find findutils: etc/cron.daily/find findutils: etc/cron.daily/find Since you've already reinstalled findutils and that didn't do it, then I'd say, Yep. Try purging and installing. I guess since this file is in /etc, it's considered a configuration file and therefore doesn't get replaced on a plain reinstall. You can always extract the file from the .deb with dpkg-deb -x and then copy it back to etc/cron.daily/ -- Chris Harris [EMAIL PROTECTED] --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locatedb is world readable
* 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 it be a solution to install slocate, and either remove the findutils (not sure if that's a good idea) or deactivate the cronjob and remove the db? Yours sincerely, Alexander signature.asc Description: Digital signature
Re: locatedb is world readable
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 to that group.) Wouldn't it be a solution to install slocate, and either remove the findutils (not sure if that's a good idea) or deactivate the cronjob and remove the db? Argh, I didn't even check that Debian has slocate. Silly me. Thanks! Regards, dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
locatedb weg
Mahlzeit, ich weiss nich warum, aber aus irgendeinem Grund wird bei mir regelmässig die Datenbank von locate geleert. Keine Ahnung und wodurch (weshalb ich ja auch eben den root's cronjobs anschauen wollte). Nachdem ich ein updatedb ausgeführt habe, klappt es auch wieder. Wenn ich dann aber 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 an [EMAIL PROTECTED] (engl)
Re: locatedb weg
From -IReturn-Receipt-To: List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED]?subject=help List-Subscribe: mailto:[EMAIL PROTECTED]?subject=subscribe List-Unsubscribe: mailto:[EMAIL PROTECTED]?subject=unsubscribe Precedence: list Resent-Sender: [EMAIL PROTECTED] Alexander Schmehl [EMAIL PROTECTED] schrieb: Mahlzeit, ich weiss nich warum, aber aus irgendeinem Grund wird bei mir regelmässig die Datenbank von locate geleert. Keine Ahnung und wodurch (weshalb ich ja auch eben den root's cronjobs anschauen wollte). Nachdem ich ein updatedb ausgeführt habe, klappt es 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 lässt sich ja so das Problem eingrenzen. Gruß, Frank -- Frank Fürst, physikalische Biochemie, Universität Potsdam, Germany Tel.: +49-331-977-5062 Fax: +49-331-977-5062 -- Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: locatedb question
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 manually, I apologize, but the transcript of what you did didn't indicate this. Sorry, I have a bad habit of not reading things fully, when I'm already typing. Drives my girlfriend nuts too. =) Just seemed logical to me that updatedb would follow it's config file updatedb.conf, is all. Thanks for the help, Mike
locatedb question
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 this as other than nobody? thanks mike
Re: locatedb question
I believe there's a restricted locate, called slocate. Then again, it looks like it's trying to do the same thing anyways, so that's what's confusing me. Fortunately, I have no shell users =) On Wed, 18 Jul 2001, Robert Waldner wrote: 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-systems, yes. Imagine files like waldner:~$ ls -al .cryptfile -rw--- 1 waldner waldner 1073741824 Jul 17 13:32 .cryptfile Well, there?s no point in making files only readable by specific users/ groups if locate would locate them just nicely for everyone ;-) cheers, rw
Re: locatedb question
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-systems, yes. Imagine files like waldner:~$ ls -al .cryptfile -rw--- 1 waldner waldner 1073741824 Jul 17 13:32 .cryptfile Well, there´s no point in making files only readable by specific users/ groups if locate would locate them just nicely for everyone ;-) cheers, rw -- -- You are in a maze of twisty little Linux distros, all different. -- Abigail, asr pgpKH2ScSWdof.pgp Description: PGP signature
Re: locatedb question
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 in /etc/updatedb.conf? Those are only noticed by the cron job, not by casual use, unless you source that file. Looking through the cron.daily, i see updatedb runs as nobody. Is there a particular danger in running this as other than nobody? I wouldn't worry about files that aren't world-readable (as another respondent suggested), but when *directories* aren't world-readable then an updatedb running as root would expose the names of files within those directories to the rest of the system. slocate remembers the permissions on directories and makes sure that it only exposes the names of files within them to users who would normally be able to see inside those directories. -- Colin Watson [EMAIL PROTECTED]
Re: locatedb question
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 where you don't even want people to know that said files exist (your pr0n directory) but your example isn't one of them. -- Alan Shutko [EMAIL PROTECTED] - In a variety of flavors! Your lucky number is 3552664958674928. Watch for it everywhere.
Re: locatedb question
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 cron job, not by casual use, unless you source that file. Well, the thing is, the only difference is that i'm running it as root, instead of nobody. The updatedb.conf is the same for both. As I said the first time, updatedb.conf isn't used in casual use of updatedb. Look at the cron job: [EMAIL PROTECTED] ~]$ 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 That '.' means that the contents of updatedb.conf are read and used to set environment variables. If you were doing this manually, I apologize, but the transcript of what you did didn't indicate this. Cheers, -- Colin Watson [EMAIL PROTECTED]
Re: locatedb question
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 some of the paths and filesystems it's told to prune in /etc/updatedb.conf? Those are only noticed by the cron job, not by casual use, unless you source that file. Well, the thing is, the only difference is that i'm running it as root, instead of nobody. The updatedb.conf is the same for both. Seeing as how i have no users, i'll likely change the runs as, to root, instead of nobody.
Re: locatedb question
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 updatedb runs as nobody. Is there a particular danger in running this as other than nobody? On your router, likely there is no harm in having a full locatedb. On a true multi-user system, users want to be able to chmod go-rwx their directories and not have the names of files still available to random other users on the system. AFAIK that is the reason. Cheers, Joost
locatedb?
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 is locatedb or locate? Where should I start reading? TIA Stephan
Re: locatedb?
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. moritz -- /* Moritz Schulte [EMAIL PROTECTED] * http://hp9001.fh-bielefeld.de/~moritz/ * PGP-Key available, encrypted Mail is welcome. */
