Bug#505446: mlocate always creates empty database

2008-11-24 Thread Adeodato Simó
* Nigel Horne [Mon, 24 Nov 2008 02:01:09 +]: > Where should I start investigating. Debian installs a *lot* of software > and I wouldn't even know where to begin. Sorry, I have no idea what software could have added those lines, they look like manual stuff to me. You could start by removing

Bug#505446: mlocate always creates empty database

2008-11-23 Thread Nigel Horne
Adeodato Simó wrote: close 505446 thanks * Nigel Horne [Thu, 20 Nov 2008 16:03:40 +]: / /./ bind bind 0 /home /home bind bind 0 These lines in /etc/fstab are the culprit: you are bind-mounting / on top of /, and /home on top of /home. Since mlocate is configured to prune

Processed: Re: Bug#505446: mlocate always creates empty database

2008-11-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > close 505446 Bug#505446: mlocate always creates empty database 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Nigel Horne <[EMAIL PROTECTED]> > thanks St

Bug#505446: mlocate always creates empty database

2008-11-23 Thread Adeodato Simó
close 505446 thanks * Nigel Horne [Thu, 20 Nov 2008 16:03:40 +]: > / /./ bind bind 0 > /home /home bind bind 0 These lines in /etc/fstab are the culprit: you are bind-mounting / on top of /, and /home on top of /home. Since mlocate is configured to prune bind mounts (PRUNE_BIND_MOUN

Bug#505446: mlocate always creates empty database

2008-11-20 Thread Nigel Horne
Can you send your /etc/fstab too? I'm curious whether the / bind mount is defined there, or some script is doing it on their own. # /etc/fstab: static file system information. # # proc/proc procdefaults0 0 /dev/sda6 /

Bug#505446: mlocate always creates empty database

2008-11-20 Thread Adeodato Simó
* Nigel Horne [Wed, 19 Nov 2008 08:12:19 +]: > Here is my /etc/mtab Can you send your /etc/fstab too? I'm curious whether the / bind mount is defined there, or some script is doing it on their own. -- Adeodato Simó dato at net.com.org.es Debian Developer

Bug#505446: mlocate always creates empty database

2008-11-20 Thread Nigel Horne
Sebastian Andrzej Siewior wrote: * Nigel Horne | 2008-11-19 08:12:19 [+]: Its a clean installation, the disc was formatted before installation. If something is wrong it's nothing I've done! Here is my /etc/mtab /dev/sda6 / ext3 rw,noatime,errors=remount-ro 0 0 tmpfs /lib/init/rw tmpfs

Bug#505446: mlocate always creates empty database

2008-11-19 Thread Sebastian Andrzej Siewior
* Nigel Horne | 2008-11-19 08:12:19 [+]: > Its a clean installation, the disc was formatted before installation. > If something is wrong it's nothing I've done! > > Here is my /etc/mtab > > /dev/sda6 / ext3 rw,noatime,errors=remount-ro 0 0 > tmpfs /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0 > p

Bug#505446: mlocate always creates empty database

2008-11-19 Thread Nigel Horne
Sebastian Andrzej Siewior wrote: * Nigel Horne | 2008-11-18 21:35:14 [+]: According to your strace output it seems that mlocate skips your root device. Could you start |/usr/bin/updatedb.mlocate --debug-pruning and paste what you get? conf_block: prune_bind_mounts\000

Bug#505446: mlocate always creates empty database

2008-11-18 Thread Sebastian Andrzej Siewior
* Nigel Horne | 2008-11-18 21:35:14 [+]: > >> According to your strace output it seems that mlocate skips your root >> device. Could you start |/usr/bin/updatedb.mlocate --debug-pruning >> >> and paste what you get? >> >> > conf_block: > prune_bind_mounts\000 you remove all bind mounts > -

Bug#505446: mlocate always creates empty database

2008-11-18 Thread Nigel Horne
According to your strace output it seems that mlocate skips your root device. Could you start |/usr/bin/updatedb.mlocate --debug-pruning and paste what you get? conf_block: prune_bind_mounts\000 1\000 \000 prunefs\000 AFS\000 AUTOFS\000 BINFMT_MISC\000 CIFS\000 CODA\000 DEVFS\000 DEVPTS\

Bug#505446: mlocate always creates empty database

2008-11-18 Thread Sebastian Andrzej Siewior
* Nigel Horne | 2008-11-13 08:07:54 [+]: > > Attached (not compressed, it's not that big!) According to your strace output it seems that mlocate skips your root device. Could you start |/usr/bin/updatedb.mlocate --debug-pruning and paste what you get? > -Nigel Sebastian -- To UNSUBSCR

Bug#505446: mlocate always creates empty database

2008-11-13 Thread Nigel Horne
It works fine on my amd64 system. Can you run as root: # strace -o strace.log /usr/bin/updatedb.mlocate and send strace.log by mail? (Compress it if it's big, please.) Attached (not compressed, it's not that big!) Thanks, -Nigel -- Nigel Horne ClamAV, The Open-Source GPL Multi-P

Bug#505446: mlocate always creates empty database

2008-11-12 Thread Adeodato Simó
* Nigel Horne [Wed, 12 Nov 2008 13:18:56 +]: Hello, > Package: mlocate > Version: 0.21.1-1 > Severity: grave > Justification: renders package unusable > /usr/bin/updatedb.mlocate always creates an empty database: > -rw-r- 1 root mlocate 235 2008-11-12 13:09 mlocate.db > It returns no er

Bug#505446: mlocate always creates empty database

2008-11-12 Thread Nigel Horne
Package: mlocate Version: 0.21.1-1 Severity: grave Justification: renders package unusable /usr/bin/updatedb.mlocate always creates an empty database: -rw-r- 1 root mlocate 235 2008-11-12 13:09 mlocate.db It returns no error status, prints no error message and immediately returns with no clue