zpool(1M) needs better exit status codes
Right now, when one uses pool import, you can't distinguish between two important, but different issues:
- A failure to import the pool itself
- A failure to enable sharing on the pool (eg. enabling a sharesmb setting failed)
Because there's no good way to distinguish these from the error status, it makes it rather hard for service start up scripts to operate without resorting to doing something like checking if the pool was imported manually by a follow up zpool import to see if the pool import part of this was actually successful. If zpool(1M) could evolve independent exit status codes for these, that might help out here.