Bug#488115: gc_approx tries to remove lost+found if cache is a separate filesystem
Package: approx Version: 3.2.0+b1 Severity: normal Hi, I have just created a filesystem for approx cache. First of all, gc_approx fails if it doesn't own lost+found. I chowned it, and now it tries to unlink lost+found (which it is denied). It sort of works now, but it would be better to not need that (chown) workaround and all... Yours, Petr. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-rc7-1-morn (PREEMPT) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages approx depends on: ii adduser 3.108 add and remove users and groups ii bzip2 1.0.5-0.1 high-quality block-sorting file co ii curl 7.18.2-1 Get a file from an HTTP, HTTPS or ii libc6 2.7-12 GNU C Library: Shared libraries ii libpcre3 7.6-2 Perl 5 Compatible Regular Expressi ii libwrap0 7.6.q-15 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-12 Linux Standard Base 3.2 init scrip approx recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488115: gc_approx tries to remove lost+found if cache is a separate filesystem
On Thu, Jun 26, 2008 at 03:54:45PM +0200, Petr Rockai wrote: I have just created a filesystem for approx cache. First of all, gc_approx fails if it doesn't own lost+found. I chowned it, and now it tries to unlink lost+found (which it is denied). It sort of works now, but it would be better to not need that (chown) workaround and all... I don't want to add code just to check for the special case where approx's cache directory is the root of an ext2/3 filesystem. An easy workaround (no chown required) is to make a top-level directory, say cache, in your dedicated filesystem, and symlink /var/cache/approx to /approx_filesystem/cache. -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488115: gc_approx tries to remove lost+found if cache is a separate filesystem
Hi, Eric Cooper [EMAIL PROTECTED] writes: I don't want to add code just to check for the special case where approx's cache directory is the root of an ext2/3 filesystem. An easy workaround (no chown required) is to make a top-level directory, say cache, in your dedicated filesystem, and symlink /var/cache/approx to /approx_filesystem/cache. a less-specific way to fix that problem would be ignoring inaccessible (ie. non-approx-owned) files and directories in there, instead of erroring out. But I won't pursue a fix for that if you disagree, feel free to close the issue in that case. -- Peter Rockai | me()mornfall!net | prockai()redhat!com http://blog.mornfall.net | http://web.mornfall.net In My Egotistical Opinion, most people's C programs should be indented six feet downward and covered with dirt. -- Blair P. Houghton on the subject of C program indentation -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
