On Mon, 12 Jul 1999 13:15:45 -0700 Ray Olszewski <[EMAIL PROTECTED]>
writes:
>Step one: give us exect error messages, not "or some such thing". You 
>
>Step two: tell us how you run pppd as root. There are many ways to run 
>pppd,
>using various helper programs (e.g., chat) and scripts. One of them 
>may have
>permissions problems. You mention ppp-on; what does it say (except for 
>your
>password, of course) and how are its permissions set?
>
ok, here is the error i get when i run pppd directly:
[foot@localhost ~]$ /usr/sbin/pppd
/usr/sbin/pppd: Can't open options file /home/foot/.ppprc: Operation not
permitted

and when i run the ppp-on script:
[foot@localhost ~]$ /etc/ppp/ppp-on
/usr/sbin/pppd: device name cannot be overridden

here are the contents of my ppp-on script
(it is basically the template that is distributed with pppd
with my info stuck in all the right places):

#!/bin/sh
#
# These are the parameters. Change as needed.
TELEPHONE=588-2300      # The telephone number for the connection
ACCOUNT=qozmo           # The account name for logon (as in 'George Burns')
PASSWORD=******         # The password for this account (and 'Gracie Allen')
LOCAL_IP=0.0.0.0        # Local IP address if known. Dynamic = 0.0.0.0
REMOTE_IP=0.0.0.0       # Remote IP address if desired. Normally 0.0.0.0
NETMASK=255.255.255.0   # The proper netmask if needed
#
# Export them so that they will be available at 'ppp-on-dialer' time.
export TELEPHONE ACCOUNT PASSWORD
# 
#
DIALER_SCRIPT=/etc/ppp/ppp-on-dialer
#
# Initiate the connection
# 
exec /usr/sbin/pppd debug lock modem crtscts /dev/ttyS2 38400 \
        asyncmap 20A0000 escape FF kdebug 0 $LOCAL_IP:$REMOTE_IP \
        noipdefault netmask $NETMASK defaultroute connect $DIALER_SCRIPT

and the ppp-on-dialer script:

#!/bin/sh
#
# This is part 2 of the ppp-on script. It will perform the connection
# protocol for the desired connection.
#
exec chat -v                                            \
        TIMEOUT         3                               \
        ABORT           '\nBUSY\r'                      \
        ABORT           '\nNO ANSWER\r'                 \
        ABORT           '\nRINGING\r\n\r\nRINGING\r'    \
        ''              \rAT                            \
        'OK-+++\c-OK'   ATH0                            \
        TIMEOUT         30                              \
        OK              ATDT$TELEPHONE                  \
        CONNECT         ''                              \
        ogin:--ogin:    $ACCOUNT                        \
        assword:        $PASSWORD



>Step three: look at your logs, and see why pppd (or chat or whatever) 
>says
>it won't run for a non-root user. This should be in /var/log/messages 
>
the log gives basically the same error given by the shell


>Step four: if minicom really can't create a lockfile, you might look 
>at why
>this is. See if, for example, the directory in which minicom wants to 
>create
>the lockfile isn't writable by the user trying to run minicom. (This 
>is only
good guess, apparently that was why.

>PS - Are you also having a problem with your keyboard?
>
very funny, u big smart azz
___________________________________________________________________
Get the Internet just the way you want it.
Free software, free e-mail, and free Internet access for a month!
Try Juno Web: http://dl.www.juno.com/dynoget/tagj.

-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]

Reply via email to