User documentation
The first line of defense against system damage is accurate and complete
documentation.
Before a command can be trusted,
its use,
behavior,
options,
and influence over the system must be fully described.
In addition to a full description of the command,
any potentially harmful behavior
should be noted,
to allow users to avoid such hazards.
Next topic:
Parameter and process attribute checking
Previous topic:
Writing trusted commands
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 27 April 2004