Linux Userspace Application Guidelines
Linux Userspace Application Guideline #1Commandline Features
Documented Product userspace commandline features are documented using installed "man pages" and will contain references to additional documentation sources (such as "info pages") as applicable.
Linux Userspace Application Guideline #2Consistent CommandLine Argument Style
Userspace commandline options are compliant with POSIX (dash prefixed) and/or GNU (dash dash prefixed) styles.
Linux Userspace Application Guideline #3Pluggable Authentication Module Compatibility
The userspace component(s) of the product authenticates users (if/when needed) using appropriate Pluggable Authentication Module (PAM) interfaces.
Linux Userspace Application Guideline #4Internationalization
Multilingual support, for the product's userspace component(s), complies with standards documented in the glibc manual.
Linux Userspace Application Guideline #5Dynamic Resource Acquisition
The product detects, and gracefully handles, any failed dynamic resource allocations. These resources include memory, sockets, disk space, etc.
Linux Userspace Application Guideline #6Forced Termination/Unload Handling
The product's userspace components gracefully self terminate upon receipt of SIGTERM, appropriately saving product data and releasing dynamically allocated resources.
Linux Userspace Application Guideline #7Datetime Handling
The userspace components of the product uses appropriate glibc calls to integrate with current time zone setting and time handling.
Linux Userspace Application Guideline #8Proper Memory Access and Manipulation
Product components do not access or manipulate memory inappropriately. This includes the following:
- For allocated memory segments, product components do not attempt to access or manipulate memory beyond the end of (or prior to) the allocated segment(s).
- Product components access memory structures and code through standard interfaces.