2006/11/23, michael <[EMAIL PROTECTED]>:
On Thu, 23 Nov 2006 12:03:49 -0700, Chris Purves wrote
> I am seeing different results from /etc/cron.daily/find and running
> updatedb from the command line:
>
> aims-07:~# /etc/cron.daily/find
> aims-07:~# locate Access.pm
> ai
On 23/11/06, Brad Sawatzky <[EMAIL PROTECTED]> wrote:
On Thu, 23 Nov 2006, michael wrote:
> On Thu, 23 Nov 2006 12:03:49 -0700, Chris Purves wrote
> > I am seeing different results from /etc/cron.daily/find and running
> > updatedb from the command line:
[ . . . ]
> &g
On Thu, 23 Nov 2006, michael wrote:
> On Thu, 23 Nov 2006 12:03:49 -0700, Chris Purves wrote
> > I am seeing different results from /etc/cron.daily/find and running
> > updatedb from the command line:
[ . . . ]
> > What are the differences between these and why does the da
On Thu, 23 Nov 2006 12:03:49 -0700, Chris Purves wrote
> I am seeing different results from /etc/cron.daily/find and running
> updatedb from the command line:
>
> aims-07:~# /etc/cron.daily/find
> aims-07:~# locate Access.pm
> aims-07:~# updatedb
> aims-07:~# locate Access.p
I am seeing different results from /etc/cron.daily/find and running
updatedb from the command line:
aims-07:~# /etc/cron.daily/find
aims-07:~# locate Access.pm
aims-07:~# updatedb
aims-07:~# locate Access.pm
/home/httpd/twiki/lib/TWiki/Access.pm
aims-07:~# /etc/cron.daily/find
aims-07:~# locate
On Mon, Mar 12, 2001 at 09:25:39PM +0100, Frederik Vanrenterghem wrote:
> Why should updatedb be run with the option --localuser=nobody ?
> Can't this be run as root, because this way, not all files on my system
> are catalogued. Is there a reason for me not to remove this option?
this is done for
Frederik Vanrenterghem wrote:
> Why should updatedb be run with the option --localuser=nobody ?
> Can't this be run as root, because this way, not all files on my system
> are catalogued. Is there a reason for me not to remove this option?
>
> Thank in advance!
>
> --
>
> --
> To UNSUBSCRIBE, emai
Why should updatedb be run with the option --localuser=nobody ?
Can't this be run as root, because this way, not all files on my system
are catalogued. Is there a reason for me not to remove this option?
Thank in advance!
--
In your /etc/passwd file, change the line for user "nobody" to have
/bin/sh as a shell instead of /dev/null, and the cron problem will go
away. This was a beta-test mistake caused by excessive security paranoia
on my part.
Of course, always make sure you understand what you are doing before you
fo
Hi,
Yes, I agree that the daily messages from cron are most
irritating, and not very infprmative. The actual source of the
problem is in /etc/passwd file, where the user nobody has been given
the shell /dev/null (this is a known problem that has been fixed in a
later version, I think, tho
David Gaudine wrote:
>
> I get this message daily:
>
> run-parts: /etc/cron.daily/find exited with return code 1
>
> /etc/cron.daily/find is;
>
> su nobody -c "cd / && updatedb" 2>/dev/null
This is a known problem. I believe it's be
I get this message daily:
From: root (Cron Daemon)
To: root
Subject: Cron <[EMAIL PROTECTED]> run-parts /etc/cron.daily
Date: Tue, 28 May 96 06:42 EDT
run-parts: /etc/cron.daily/find exited with return code 1
/etc/cron.daily/find is;
#! /bin/sh
#
# cron
In article <[EMAIL PROTECTED]> you write:
[...]
>
>This raises a question with me. If I understand how debian works, even when
>a fixed base pkg gets updated on a debian system, this error with user nobody
>will still be there since it won't overwrite the passwd file. This isn't the
>best example o
>
> This bug was in the passwd file from the base package.
>
> It can be fixed by replacing the nobody line in /etc/passwd with this entry:
>
> nobody:*:65534:65534:nobody:/dev/null:
>
> Hope that helps.
> Susan Kleinmann
> [EMAIL PROTECTED]
>
>
I have already bug-reported this and it's bein
Hello,
> I just changed "su nobody" to "su root". I can run it manually now as
> root so I assume cron should run it OK next time around.
Dont do this. The entries in the find.codes database are public, therefore
there should be no informatiuon stored normal users are unable to see (i.e.
filenam
This bug was in the passwd file from the base package.
It can be fixed by replacing the nobody line in /etc/passwd with this entry:
nobody:*:65534:65534:nobody:/dev/null:
Hope that helps.
Susan Kleinmann
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
>
> Rick> Is this a problem with the cron job from the findutils package or the
> Rick> passwd file from the base package?
>
> With the passwd file. There is a : missing at the end of the nobody entry.
> It should be
> nobody:*:65534:65534:nobody:/dev/null:
H
/etc/cron.daily/find looks like this:
#! /bin/sh
#
# cron script to update the `find.codes' database.
#
# Written by Ian A. Murdock <[EMAIL PROTECTED]>.
su nobody -c "cd / && updatedb" 2>/dev/null
but the "nobody" entry in /etc/passwd looks like th
18 matches
Mail list logo
