Release zpool resources when finished updates
It's not documented but it's obvious that zpool_iter expects the callback to call zpool_close to release resources associated with the zpool - it's not a problem for short-lived commands like zpool(1) but it leaks memory like a firehose.
Release zpool resources when finished updates
It's not documented but it's obvious that zpool_iter expects the
callback to call zpool_close to release resources associated with
the zpool - it's not a problem for short-lived commands like zpool(1)
but it leaks memory like a firehose.