Bug#505446: mlocate always creates empty database
* 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 them and see if your system boots, which it should... -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Enrique Bunbury - Luna -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
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_MOUNTS=yes in updatedb.conf), and the root directory is a bind mount, *everything* gets prunned. I have no idea why would your system be doing such thing. You should investigate why those lines are there and/or remove them or, alternatively, set PRUNE_BIND_MOUNTS=no in your updatedb.conf). Hope this helps; in the meantime, I'm marking this bug as closed. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Dar Williams - What Do You Love More Than Love -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
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 bind mounts (PRUNE_BIND_MOUNTS=yes in updatedb.conf), and the root directory is a bind mount, *everything* gets prunned. I have no idea why would your system be doing such thing. You should investigate why those lines are there and/or remove them or, alternatively, set PRUNE_BIND_MOUNTS=no in your updatedb.conf). Where should I start investigating. Debian installs a *lot* of software and I wouldn't even know where to begin. Hope this helps; in the meantime, I'm marking this bug as closed. Why? Clearly there's a bug somewhere!!! -- Nigel Horne ClamAV, The Open-Source GPL Multi-Platform Anti-Virus tool-kit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
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 rw,nosuid,mode=0755 0 0 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 procbususb /proc/bus/usb usbfs rw 0 0 udev /dev tmpfs rw,mode=0755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0 fusectl /sys/fs/fuse/connections fusectl rw 0 0 /dev/sdb2 /home ext3 rw,noatime 0 0 /dev/sda2 /mnt/c fuseblk rw,allow_other,blksize=4096 0 0 /dev/sdb1 /mnt/d fuseblk rw,allow_other,blksize=4096 0 0 / / bind rw,bind 0 0 /home /home bind rw,bind 0 0 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0 automount(pid3573) /net autofs rw,fd=4,pgrp=3573,minproto=2,maxproto=4 0 0 automount(pid3544) /smb autofs rw,fd=4,pgrp=3544,minproto=2,maxproto=4 0 0 You have your / and /home mounted onto itself + you have automount on /net and /smb. This is not part of the a standard installation. Either you have it by accident in your fstab or a chroot mount script went wrong. I guess the latter. Does your /proc/mounts contain a line like |tmpfs / tmpfs rw,size=10240k,mode=755 0 0 ? If so, than this is a *valid* bind mount. No it doesn't. Sebastian -- Nigel Horne ClamAV, The Open-Source GPL Multi-Platform Anti-Virus tool-kit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
* 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 adeodato at debian.org The problem I have with making an intelligent statement is that some people then think that it's not an isolated occurrance. -- Simon Travaglia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
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. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/sda6 / ext3errors=remount-ro,noatime 0 1 /dev/sdb2 /home ext3noatime0 2 /dev/sda5 noneswapsw 0 0 /dev/hdc/media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/sda2/mnt/cntfs-3gdefaults,umask=0,nls-utf800 /dev/sdb1/mnt/dntfs-3gdefaults,umask=0,nls-utf800 / /./ bind bind 0 /home /home bind bind 0 -- Nigel Horne ClamAV, The Open-Source GPL Multi-Platform Anti-Virus tool-kit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
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 you remove all bind mounts --- Rebuilding bind_mount_paths: `/', opts `rw,noatime,errors=remount-ro' `/lib/init/rw', opts `rw,nosuid,mode=0755' `/proc', opts `rw,noexec,nosuid,nodev' `/sys', opts `rw,noexec,nosuid,nodev' `/proc/bus/usb', opts `rw' `/dev', opts `rw,mode=0755' `/dev/shm', opts `rw,nosuid,nodev' `/dev/pts', opts `rw,noexec,nosuid,gid=5,mode=620' `/sys/fs/fuse/connections', opts `rw' `/home', opts `rw,noatime' `/mnt/c', opts `rw,allow_other,blksize=4096' `/mnt/d', opts `rw,allow_other,blksize=4096' `/', opts `rw,bind' = adding `/' `/home', opts `rw,bind' = adding `/home' `/var/lib/nfs/rpc_pipefs', opts `rw' `/net', opts `rw,fd=4,pgrp=3012,minproto=2,maxproto=4' `/smb', opts `rw,fd=4,pgrp=2980,minproto=2,maxproto=4' ...done Skipping `/': bind mount and your root is bind mounted. Your setup may be be broken somehow. I guess your / mount point is twice in /etc/mtab with ext3 and with a bind mount. Once you get rid of this, your mlocate will work again. Do you have a special fstab, initrd hooks or something else that would explain it? Maybe it is a leftover from an earlier install and will work once you remove that line. 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 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 procbususb /proc/bus/usb usbfs rw 0 0 udev /dev tmpfs rw,mode=0755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0 fusectl /sys/fs/fuse/connections fusectl rw 0 0 /dev/sdb2 /home ext3 rw,noatime 0 0 /dev/sda2 /mnt/c fuseblk rw,allow_other,blksize=4096 0 0 /dev/sdb1 /mnt/d fuseblk rw,allow_other,blksize=4096 0 0 / / bind rw,bind 0 0 /home /home bind rw,bind 0 0 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0 automount(pid3573) /net autofs rw,fd=4,pgrp=3573,minproto=2,maxproto=4 0 0 automount(pid3544) /smb autofs rw,fd=4,pgrp=3544,minproto=2,maxproto=4 0 0 Sebastian -- Nigel Horne ClamAV, The Open-Source GPL Multi-Platform Anti-Virus tool-kit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
* 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 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 procbususb /proc/bus/usb usbfs rw 0 0 udev /dev tmpfs rw,mode=0755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0 fusectl /sys/fs/fuse/connections fusectl rw 0 0 /dev/sdb2 /home ext3 rw,noatime 0 0 /dev/sda2 /mnt/c fuseblk rw,allow_other,blksize=4096 0 0 /dev/sdb1 /mnt/d fuseblk rw,allow_other,blksize=4096 0 0 / / bind rw,bind 0 0 /home /home bind rw,bind 0 0 rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0 automount(pid3573) /net autofs rw,fd=4,pgrp=3573,minproto=2,maxproto=4 0 0 automount(pid3544) /smb autofs rw,fd=4,pgrp=3544,minproto=2,maxproto=4 0 0 You have your / and /home mounted onto itself + you have automount on /net and /smb. This is not part of the a standard installation. Either you have it by accident in your fstab or a chroot mount script went wrong. I guess the latter. Does your /proc/mounts contain a line like |tmpfs / tmpfs rw,size=10240k,mode=755 0 0 ? If so, than this is a *valid* bind mount. Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
* 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 UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
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\000 FTPFS\000 ISO9660\000 LUSTRE_LITE\000 MFS\000 NCPFS\000 NFS\000 NFS4\000 PROC\000 RPC_PIPEFS\000 SHFS\000 SMBFS\000 SYSFS\000 TMPFS\000 UDF\000 USBFS\000 \000 prunenames\000 \000 prunepaths\000 /media\000 /tmp\000 /var/spool\000 \000 --- Rebuilding bind_mount_paths: `/', opts `rw,noatime,errors=remount-ro' `/lib/init/rw', opts `rw,nosuid,mode=0755' `/proc', opts `rw,noexec,nosuid,nodev' `/sys', opts `rw,noexec,nosuid,nodev' `/proc/bus/usb', opts `rw' `/dev', opts `rw,mode=0755' `/dev/shm', opts `rw,nosuid,nodev' `/dev/pts', opts `rw,noexec,nosuid,gid=5,mode=620' `/sys/fs/fuse/connections', opts `rw' `/home', opts `rw,noatime' `/mnt/c', opts `rw,allow_other,blksize=4096' `/mnt/d', opts `rw,allow_other,blksize=4096' `/', opts `rw,bind' = adding `/' `/home', opts `rw,bind' = adding `/home' `/var/lib/nfs/rpc_pipefs', opts `rw' `/net', opts `rw,fd=4,pgrp=3012,minproto=2,maxproto=4' `/smb', opts `rw,fd=4,pgrp=2980,minproto=2,maxproto=4' ...done Skipping `/': bind mount Hope that helps. -- Nigel Horne ClamAV, The Open-Source GPL Multi-Platform Anti-Virus tool-kit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
* 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 --- Rebuilding bind_mount_paths: `/', opts `rw,noatime,errors=remount-ro' `/lib/init/rw', opts `rw,nosuid,mode=0755' `/proc', opts `rw,noexec,nosuid,nodev' `/sys', opts `rw,noexec,nosuid,nodev' `/proc/bus/usb', opts `rw' `/dev', opts `rw,mode=0755' `/dev/shm', opts `rw,nosuid,nodev' `/dev/pts', opts `rw,noexec,nosuid,gid=5,mode=620' `/sys/fs/fuse/connections', opts `rw' `/home', opts `rw,noatime' `/mnt/c', opts `rw,allow_other,blksize=4096' `/mnt/d', opts `rw,allow_other,blksize=4096' `/', opts `rw,bind' = adding `/' `/home', opts `rw,bind' = adding `/home' `/var/lib/nfs/rpc_pipefs', opts `rw' `/net', opts `rw,fd=4,pgrp=3012,minproto=2,maxproto=4' `/smb', opts `rw,fd=4,pgrp=2980,minproto=2,maxproto=4' ...done Skipping `/': bind mount and your root is bind mounted. Your setup may be be broken somehow. I guess your / mount point is twice in /etc/mtab with ext3 and with a bind mount. Once you get rid of this, your mlocate will work again. Do you have a special fstab, initrd hooks or something else that would explain it? Maybe it is a leftover from an earlier install and will work once you remove that line. Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
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-Platform Anti-Virus tool-kit
execve(/usr/bin/updatedb.mlocate, [/usr/bin/updatedb.mlocate], [/* 50 vars */]) = 0
brk(0) = 0x23bd000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f37c619
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f37c618e000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=67876, ...}) = 0
mmap(NULL, 67876, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f37c617d000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\300\342\1\0\0\0\0\0@..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1375536, ...}) = 0
mmap(NULL, 3482232, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f37c5c23000
mprotect(0x7f37c5d6d000, 2093056, PROT_NONE) = 0
mmap(0x7f37c5f6c000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x149000) = 0x7f37c5f6c000
mmap(0x7f37c5f71000, 17016, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f37c5f71000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f37c617c000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f37c617b000
arch_prctl(ARCH_SET_FS, 0x7f37c617b6e0) = 0
mprotect(0x7f37c5f6c000, 12288, PROT_READ) = 0
munmap(0x7f37c617d000, 67876) = 0
brk(0) = 0x23bd000
brk(0x23de000) = 0x23de000
open(/usr/lib/locale/locale-archive, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=1282800, ...}) = 0
mmap(NULL, 1282800, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f37c6041000
close(3)= 0
open(/etc/updatedb.conf, O_RDONLY)= 3
fstat(3, {st_mode=S_IFREG|0644, st_size=248, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f37c618d000
read(3, PRUNE_BIND_MOUNTS=\yes\\n# PRUNENA..., 4096) = 248
read(3, ..., 4096)= 0
close(3)= 0
munmap(0x7f37c618d000, 4096)= 0
stat(/etc/mtab, {st_mode=S_IFREG|0644, st_size=808, ...}) = 0
open(/etc/mtab, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=808, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f37c618d000
read(3, /dev/sda6 / ext3 rw,noatime,error..., 4096) = 808
lstat(/home, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
read(3, ..., 4096)= 0
close(3)= 0
munmap(0x7f37c618d000, 4096)= 0
open(/var/lib/mlocate/mlocate.db, O_RDWR) = 3
read(3, \0mlocate\0\0\0\331\0\1\0\0/\0prune_bind_moun..., 8192) = 235
read(3, ..., 8192)= 0
fcntl(3, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = 0
rt_sigaction(SIGABRT, {0x403d40, [INT ABRT TERM], SA_RESTORER, 0x7f37c5c54f60}, NULL, 8) = 0
rt_sigaction(SIGINT, {0x403d40, [INT ABRT TERM], SA_RESTORER, 0x7f37c5c54f60}, NULL, 8) = 0
rt_sigaction(SIGTERM, {0x403d40, [INT ABRT TERM], SA_RESTORER, 0x7f37c5c54f60}, NULL, 8) = 0
getpid()= 4861
open(/var/lib/mlocate/mlocate.db.EhRV9C, O_RDWR|O_CREAT|O_EXCL, 0600) = 4
rt_sigprocmask(SIG_BLOCK, [INT ABRT TERM], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f37c618d000
lseek(4, 0, SEEK_CUR) = 0
chdir(/) = 0
lstat(., {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat(/etc/mtab, {st_mode=S_IFREG|0644, st_size=808, ...}) = 0
write(4, \0mlocate\0\0\0\331\0\1\0\0/\0prune_bind_moun..., 235) = 235
close(4)= 0
munmap(0x7f37c618d000, 4096)= 0
socket(PF_FILE, SOCK_STREAM, 0) = 4
fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(4, {sa_family=AF_FILE, path=/var/run/nscd/socket...}, 110) = -1 ENOENT (No such file or directory)
close(4)= 0
socket(PF_FILE, SOCK_STREAM, 0) = 4
fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(4, {sa_family=AF_FILE, path=/var/run/nscd/socket...}, 110) = -1 ENOENT (No such file or directory)
close(4)= 0
Bug#505446: mlocate always creates empty database
* 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 error status, prints no error message and immediately returns with no clue what's wrong. It works fine on my 32 bit machine. 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.) Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Elton John - House -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505446: mlocate always creates empty database
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 what's wrong. It works fine on my 32 bit machine. packard:/var/lib/mlocate# time /usr/bin/updatedb.mlocate real0m0.003s user0m0.004s sys 0m0.000s packard:/var/lib/mlocate# echo $? 0 packard:/var/lib/mlocate# -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mlocate depends on: ii adduser 3.110 add and remove users and groups ii libc6 2.7-15 GNU C Library: Shared libraries mlocate recommends no packages. mlocate suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
