R. D. Loga wrote:
When a non-root user types pon at the prompt they get Connect script
failed. Pon works fine for the root user. I changed several file
permissions to get this far. Do I have to change permissions on all the
scripts in /etc/ppp/ip-up.d directory too? Is there an easy way
Quoting Bolan Meek ([EMAIL PROTECTED]):
R. D. Loga wrote:
When a non-root user types pon at the prompt they get Connect script
failed. Pon works fine for the root user. I changed several file
permissions to get this far. Do I have to change permissions on all the
scripts in
When a non-root user types pon at the prompt they get Connect script
failed. Pon works fine for the root user. I changed several file
permissions to get this far. Do I have to change permissions on all the
scripts in /etc/ppp/ip-up.d directory too? Is there an easy way to allow
non-root users
On Tue, Jul 25, 2000 at 08:04:30PM -0500, R. D. Loga wrote:
When a non-root user types pon at the prompt they get Connect script
failed. Pon works fine for the root user. I changed several file
permissions to get this far. Do I have to change permissions on all
the scripts in
: Non-root user executing pon
On Tue, Jul 25, 2000 at 08:04:30PM -0500, R. D. Loga wrote:
When a non-root user types pon at the prompt they get Connect script
failed. Pon works fine for the root user. I changed several file
permissions to get this far. Do I have to change permissions on all
I haven't used ppp with Debian, but I understood that permission to
activate it was set in the same way as other resource accesses, such as
sound - all you need to do is add the user to the appropriate group.
For example: to allow myself to use the sound card while a normal user,
I just added
R. D. Loga writes:
I ran pppconfig but found no option to add a ppp user.
That option is in the version of pppconfig in unstable.
I had already made the user a member of the dip and dialout groups.
I think you have an old version of the ppp package that sets the
permissions on
7 matches
Mail list logo
