bozo: do not fail silently on unknown bosserver options 30/12630/3
authorMichael Meffie <mmeffie@sinenomine.net>
Fri, 2 Jun 2017 19:19:26 +0000 (15:19 -0400)
committerBenjamin Kaduk <kaduk@mit.edu>
Sun, 4 Jun 2017 17:14:24 +0000 (13:14 -0400)
commitf5491119ff7d422b1c0c311a50e30bec1c15296c
tree93138f4b396528086c5028b0f8a6477f5193b885
parentaaa47dc1077f0dd5b0040006c831f64cc8a303b5
bozo: do not fail silently on unknown bosserver options

Instead of failing silently when the bosserver is started with an
unknown option, print an error message and exit with a non-zero value.
Continue to exit with 0 when the -help option is given to request the
usage message.

This change should help make bosserver startup failures more obvious
when an unsupported option is specified. Example systemd status message:

   systemd[1]: Starting OpenAFS Server Service...
   bosserver[32308]: Unrecognized option: -bogus
   bosserver[32308]: Usage: bosserver [-noauth] ....
   systemd[1]: openafs-server.service: main process exited,
               code=exited, status=1/FAILURE

Change-Id: I8717fb4a788fbcc3d1e2d271dd03511c5b504f10
Reviewed-on: https://gerrit.openafs.org/12630
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
src/bozo/bosserver.c