The transition to the new exec policy in RC2's rmid is likely to yield confusion,
especially if rmid is run with no arguments.

In the new scheme, running rmid with no arguments is probably a mistake, but
could possibly be exactly what the user is looking for.

RMID should check during startup to see if an execPolicy or security policy was
set, and if neither was set, should print out a helpful warning message directing
the user to the tool documentation with a brief explanation of the errors to
expect (AccessControlExceptions naming rmid's new Permissions).