pfexec's error reporting is (at least sometimes) awful
A SmartOS user was confused about how precisely to invoke pfexec(1M), and did this
> pfexec -P "Primary Administrator" id setppriv(): Bad address
The error here is that -P takes privileges, not profile names. The error message should, well, say something similar to that. Probably "unknown privilege: <thing>" or if necessary a generic message regarding the parsing failing.
Also (and perhaps a separate bug, but I think it's related) the manual page for pfexec(1M) is pretty much moonspeak unless you already understand how all this works, which doesn't help in the slightest.
Updated by Electric Monk over 7 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
commit 511ef1d6e74f3d1db7bd854375a0926d87bdd7e6 Author: Gary Mills <firstname.lastname@example.org> Date: 2014-06-21T17:24:43.000Z 4577 pfexec's error reporting is (at least sometimes) awful Reviewed by: Jason King <email@example.com> Reviewed by: Adam Števko <firstname.lastname@example.org> Approved by: Robert Mustacchi <email@example.com>