If the PPP connection is initiated by the serial port monitor (ttymon) or the ISDN monitor (isdnmon) automatically detecting PPP data, the monitor first performs call filtering (see Callfilter(4bnu)) before executing pppsh directly (see Autoacts(4bnu)). Login authentication is not performed but CHAP or PAP authentication must be performed during negotiation of the PPP link.
If the PPP connection is initiated by logging in using a ``chat script'', the monitor first performs call filtering (see Callfilter(4bnu)), and then starts any services that are defined for the serial port or ISDN device in the Callservices(4bnu) file. If users can either log in remotely using PPP or locally using a login shell such as ksh, Callservices should contain entries to start /bin/pppsh for the serial ports or ISDN devices which will be used for remote access. If Callservices does not define any entries for the serial ports or ISDN devices that will be used, or the entries start the shell server (see shserv(1M)), the /etc/passwd entry for the remote user must define /bin/pppsh as its login shell if a PPP session is to be initiated. In all cases, login authenticates the supplied password. If successful, CHAP or PAP authentication may also be performed during negotiation of the PPP link.
The -d option generates debugging information in syslog.