Package: zfs-fuse
Version: 0.6.0+critical20100301-3
Severity: wishlist
Hi.
In case zfs-fuse was disabled via ENABLE_ZFS, the init script is
quite chatty by printing out the whole story why it is not started:
if [ "x$ENABLE_ZFS" != "xyes" ]; then
echo "Not starting $NAME: ENABLE_ZFS is not set to 'yes' in
/etc/default/$NAME" >&2
return 1
fi
Is this really necessary? A sysadmin usually disabled it by intention
and therefore knows what happens, and even if not, such information
belongs to man pages.
I guess, a simple: ... disabled.
would be enough.
btw: Throughout the whole initscript, why are you using
an "x" in things like "x$ENABLE_ZFS" != "xyes"??
As you're having quotes around, this shouldn't be necessary, even if
ENABLE_ZFS is empty/undefined... and it's quite ugly to read.
Cheers,
Chris.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33-heisenberg (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages zfs-fuse depends on:
ii fuse-utils 2.8.1-1.2 Filesystem in USErspace (utilities
ii libaio1 0.3.107-7 Linux kernel AIO access library -
ii libc6 2.10.2-8 Embedded GNU C Library: Shared lib
ii libfuse2 2.8.1-1.2 Filesystem in USErspace library
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
zfs-fuse recommends no packages.
zfs-fuse suggests no packages.
-- Configuration Files:
/etc/default/zfs-fuse changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
