PPP driver-
The driver information is available through syslog.
The driver passes its debugging information to the PPP daemon
that actually logs the information to /usr/adm/syslog;
therefore, the log identifies the information as coming from pppd.
The driver logs information on a per-link basis, so an individual
link can be debugged.
The amount of information that the driver logs about a link is
configurable on an unestablished link
using the PPP Manager.
The change to the debug level takes effect the next
time the link is established.
To change the debug value of an established link, enter the
following command:
ifconfig interface debug debug_number
interface must be an established PPP
interface such as ppp0 and debug_number a value of
0, 1, or 2.
PPP daemon-
Information from the PPP daemon
is available through syslog.
The amount of information logged depends on the debug level which can be
set using the -d option to
pppd(ADMN).
pppd generates four types of messages: ``warnings'',
``errors'', ``alerts'', and ``info''.
pppd always logs all ``warning'', ``error'', and
``alert'' messages.
pppd logs ``info'' messages according to the debug level.
The default debug level of 0 disables ``info'' messages.
A level greater than 0 allows ``info'' messages to be logged.
To turn on logging of ``info'' messages, enter the following command:
kill -16 `cat /etc/pppd.pid`
To turn off logging of ``info'' messages:
kill -17 `cat /etc/pppd.pid`
These commands also affect the logging of UUCP activity.
UUCP-
When PPP requests a UUCP link, the UUCP activity is logged to the
system console (/dev/tty01).
The amount of information logged depends on the value of
the daemon debug level described above.
Recognized numbers are 1 to 9, with higher numbers logging more
UUCP information.
The UUCP logging level is increased by 1 up to a maximum of 9,
each time you enter the following command:
kill -16 `cat /etc/pppd.pid`
To turn off UUCP logging, enter:
kill -17 `cat /etc/pppd.pid`.