Package: lvm2 Version: 2.02.06-4 The lvm utilities apparently whinge if they inherit any fds other than 0,1,2. This is quite unreasonable. There is nothing wrong with executing a program with some inherited fd >2 and there are many reasons why one might want to do so.
If lvm needs to fork off a daemon or some such then fine, it ought to close them, but it should do so silently. Ian. [EMAIL PROTECTED]:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% adt_gutsy_base glalonde -wi-a- 3.00G adt_gutsy_cowdata glalonde -wi-a- 2.50G bigscratch glalonde -wi-a- 10.00G [EMAIL PROTECTED]:~# lvs 3>/dev/null File descriptor 3 left open LV VG Attr LSize Origin Snap% Move Log Copy% adt_gutsy_base glalonde -wi-a- 3.00G adt_gutsy_cowdata glalonde -wi-a- 2.50G bigscratch glalonde -wi-a- 10.00G [EMAIL PROTECTED]:~# dpkg -s lvm2 Package: lvm2 Status: install ok installed Priority: optional Section: admin Installed-Size: 848 Maintainer: Debian LVM Team <[EMAIL PROTECTED]> Architecture: i386 Version: 2.02.06-4 Provides: lvm-binaries Depends: libc6 (>= 2.3.6-6), libdevmapper1.02 (>= 2:1.02.02-2), libncurses5 (>= 5.4-5), libreadline5 (>= 5.2), libselinux1 (>= 1.32), libsepol1 (>= 1.14), lvm-common (>> 1.5.8) Pre-Depends: debconf (>= 1.4.69) | debconf-2.0 Suggests: dmsetup Conffiles: /etc/lvm/lvm.conf 69799c527604d709cadde015d4d82135 Description: The Linux Logical Volume Manager This is LVM2, the rewrite of The Linux Logical Volume Manager. LVM supports enterprise level volume management of disk and disk subsystems by grouping arbitrary disks into volume groups. The total capacity of volume groups can be allocated to logical volumes, which are accessed as regular block devices. [EMAIL PROTECTED]:~# -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
