PPS interface to the network manager
Syntax:
net_pps [-A addr:port] [-a]
[-c file] [-d] [if0...] [-m]
[-P script] [-p prefix] [-r name [if0...]]
[-S uid] [-s] [-u] &
Options:
- -A addr:port
- Proxy to publish to when proxy authentication is required.
- -a
- Automatically configure any discovered interfaces when the link state indicates that the
interfaces are connected.
- -d
- Enable debug messages (to stdout).
- if0...
- Specify prioritized list of interfaces to be considered for multihomed operation,
preference of default routes, confstr resolver configuration, etc.
- -m
- Use multipath routes.
- -P script
- Specify the script to run for updating proxy settings.
- -p prefix
- Add this prefix to all executable paths. This has no effect without the
-s option.
- -r name [if0...]
- Create another routing domain (called name) with the following
prioritized interface list.
- -S uid
- Run subprocesses as this uid.
- -s
- Use standard filepaths for subprocess executables (defaults:
system=/usr/sbin/ user=/usr/bin/).
- -u
- Automatically assume the interface is connected based on its up state. This
allows shim drivers as well as drivers that don't issue link state changes to work.
Description:
The net_pps service offers a PPS interface for communicating with the QNX network manager. For more information about QNX support for networking, see "Networking Architecture" in the System Architecture
Guide.
PPS objects:
For more information about the instructions
net_pps can send to the network manager and the information it can
receive, see the relevant PPS object and directory descriptions: