Your message dated Tue, 27 Jan 2009 20:02:02 GMT
with message-id <[email protected]>
and subject line slocate has been removed from Debian, closing #240370
has caused the Debian Bug report #240370,
regarding Contrib: cron script for partial updating
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
240370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=240370
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: slocate
Version: 2.7-2
Severity: wishlist

Slocate updates its database daily which results in prolonged
heavy disk activity. This may not matter for machines where
the update is done at a time when no one is actually using the
system. For those like me who switch on their box in the
morning it can be somewhat annoying.

On my system I have areas where changes are frequent and
others, where changes are not that frequent or where I'm 
willing to tolerate a slightly out-of-date slocate index.
Accordingly, I've attached a script that enables admins to
decide which directories are updated daily and which only
at a longer interval. Please consider including the script
as a contribution with the slocate package.

As the script creates multiple databases, currently users
would have to set their LOCATE_PATH explicitly like this

export 
LOCATE_PATH="/var/lib/slocate/slocate.home.db:/var/lib/slocate/slocate.db"

To make this unnecessary, I suggest that slocate by default
add all databases in /var/lib/slocate/ in order of recency.


Michael


---------- /etc/default/slocate ----------
# Update the full index every $FULL_UPDATE_INTERVAL days.
# If left empty or undefined, the update is done daily.
FULL_UPDATE_INTERVAL=5

# Directories whose file indexes should be updated daily.
# If left empty or undefined, everything starting at /
# is indexed.
# Multiple directories are separated by whitespace
# e.g., "/dir1 /dir2"
UPDATE_DAILY="/home"


---------- /etc/cron.daily/slocate ----------
#! /bin/sh

UPDATE=/usr/bin/updatedb
SLOCATEDB_DIR=/var/lib/slocate
MAIN_SLOCATEDB=$SLOCATEDB_DIR/slocate.db

[ -r /etc/default/slocate ] && . /etc/default/slocate

if [ -x /usr/bin/slocate ]
then
        if [ ! -f /etc/updatedb.conf ]
        then
                UPDATE="$UPDATE -f proc"
        fi
        for d in $UPDATE_DAILY; do
                n=`echo $d | sed -e 's,^/,,;s,/,_,g'`
                db=$SLOCATEDB_DIR/slocate.$n.db
                $UPDATE -U $d -o $db
                chown root.slocate $db
        done
        if [ -z "$FULL_UPDATE_INTERVAL" \
                 -o "`find $MAIN_SLOCATEDB -daystart -mtime 
-$FULL_UPDATE_INTERVAL 2>/dev/null`" \
                        != "$MAIN_SLOCATEDB" ]
        then
                excl=`echo $UPDATE_DAILY | sed -e 's/^ *//;s/ *$//;s/  */,/g'`
                $UPDATE -u -e $excl -o $MAIN_SLOCATEDB
                chown root:slocate $MAIN_SLOCATEDB
        fi
fi



-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.4
Locale: LANG=POSIX, lc_ctype=de_de.iso885...@euro

Versions of packages slocate depends on:
ii  adduser                     3.51         Add and remove users and groups
ii  dpkg                        1.10.20      Package maintenance system for Deb
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 3.1-1.1+rm

The slocate package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/457565 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

Kind regards,
--
Marco Rodrigues


--- End Message ---

Reply via email to