Harri Porten <[EMAIL PROTECTED]> wrote:
> I could explain the behaviour if he's using kppp in conjunction with
> pppd-2.3.6 or higher. kppp from KDE 1.1 binds stdin/stdout the serial
> device _and_ explicitly specifies the /dev/ttySx in the command line.
pppd does try to check for this but current versions get fooled when
the device name you specify (e.g. /dev/modem) is a link to the device
which is open on stdin (e.g. /dev/ttyS0).
> This leads to some trouble with the recent pppd's since will sent its
> debug output to the serial port this way. The solution would be to
> disable all debugging (see kppprc), get the most recent version from
> ftp.kde.org or wait for KDE 1.1.1.
Another point is that pppd doesn't lock the device if it is using the
device which is already open on stdin (even if the lock option is
given). If kppp runs pppd with the serial port open on stdin and
already locked, then somebody should change it so it doesn't give that
annoying message on startup about having to remove the lock option
from /etc/ppp/options.
Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
