From owner-freebsd-hackers Tue Oct 6 18:35:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24873 for freebsd-hackers-outgoing; Tue, 6 Oct 1998 18:35:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24793 for ; Tue, 6 Oct 1998 18:35:18 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id VAA21131 for ; Tue, 6 Oct 1998 21:34:39 -0400 (EDT) Date: Tue, 6 Oct 1998 21:34:39 -0400 (EDT) From: Chuck Robey To: hackers@FreeBSD.ORG Subject: ppp incoming question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How come, when you're setting up an incoming (user ppp) connection, you have to use a /usr/local/bin/ppplogin script? The script just invokes "ppp -direct incoming", and I wonder why you couldn't just edit that line into the shell field of the passwd (via vipw). Would there be some kind of permission problem? I'm thinking of doing something like that, with chap user IDing, so I wouldn't need separate logins, and I'd want to eliminate any intervening files if I can. If I _have_ to have the file, what permissions and what user/group should be set on the file? BTW, I got all this from the ppp manpage. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message