> I would much prefer to do > > for snap in $(zfs list -t snapshot -r foo/bar ) > do > zfs destroy -t snapshot $snap > do > > the not have the -t. Especially the further away the destroy is from the > generation of the list. The extra -t would be belt and braces but that is > how I like my data protected.
Especially if we imagine that someone further down the line decides to slightly modify the format of the "zfs list -t snapshot" output - such as by having it give a hierarchal view with the roots being the filesystem path... This is of course a normal problem with shell scripting (unless the zfs command is documented to guarantee backward compatible output?), but in cases like this it really really becomes critical. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org
signature.asc
Description: OpenPGP digital signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
