From owner-freebsd-hackers Tue Oct 6 22:28:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09877 for freebsd-hackers-outgoing; Tue, 6 Oct 1998 22:28:36 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles29.castles.com [208.214.165.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09871 for ; Tue, 6 Oct 1998 22:28:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00386; Tue, 6 Oct 1998 22:31:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810070531.WAA00386@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: hackers@FreeBSD.ORG Subject: Re: ppp incoming question In-reply-to: Your message of "Tue, 06 Oct 1998 21:34:39 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 Oct 1998 22:31:35 -0700 From: Mike Smith 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. Because the shell field specifies the shell, not its arguments. > If I _have_ to have the file, what permissions and what user/group > should be set on the file? It's not really important, as long as it's executable by the user logging in. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message