Your message dated Thu, 27 Dec 2007 19:23:03 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#457882: findutils: setting LOCALUSER in
/etc/cron.daily/find has no effect
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: findutils
Version: 4.2.28-1
Severity: normal
The lines
LOCALUSER="nobody"
export LOCALUSER
in /etc/cron.daily/find have no effect, because ubdatedb gets the
value set in /etc/updatedb.conf instead.
You could either test in updatedb.conf to see whether this environmental
parameter has been set, or omit the "export" and instead use an option
--localuser=$LOCALUSER for the updatedb command in /etc/cron.daily/find
(because the command-line option will override the environmental
variable).
Clearly there's a policy issue here: which of these configuration files
should take precedence?
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages findutils depends on:
ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries
findutils recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.2.31-2
On 2007-12-26 "Andrew T. Young" <[EMAIL PROTECTED]> wrote:
> Package: findutils
> Version: 4.2.28-1
> Severity: normal
> The lines
> LOCALUSER="nobody"
> export LOCALUSER
> in /etc/cron.daily/find have no effect, because ubdatedb gets the
> value set in /etc/updatedb.conf instead.
> You could either test in updatedb.conf to see whether this environmental
> parameter has been set, or omit the "export" and instead use an option
> --localuser=$LOCALUSER for the updatedb command in /etc/cron.daily/find
> (because the command-line option will override the environmental
> variable).
> Clearly there's a policy issue here: which of these configuration files
> should take precedence?
[...]
This has been fixed in 4.2.31-2. /etc/updatedb.conf is used no more.
cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
