From owner-freebsd-questions@FreeBSD.ORG Fri Aug 14 11:49:49 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD74E106568C for ; Fri, 14 Aug 2009 11:49:49 +0000 (UTC) (envelope-from alex@mailinglist.ahhyes.net) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.freebsd.org (Postfix) with ESMTP id 50BBC8FC16 for ; Fri, 14 Aug 2009 11:49:48 +0000 (UTC) Received: from [172.16.0.201] (c122-106-58-139.rivrw1.nsw.optusnet.com.au [122.106.58.139]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n7EBnkmC004907 for ; Fri, 14 Aug 2009 21:49:47 +1000 Message-ID: <4A854F5C.3010003@mailinglist.ahhyes.net> Date: Fri, 14 Aug 2009 21:49:48 +1000 From: Alex R User-Agent: Thunderbird 2.0.0.22 (X11/20090608) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4A851E30.2010008@mailinglist.ahhyes.net> <20090814111508.GA9600@ei.bzerk.org> In-Reply-To: <20090814111508.GA9600@ei.bzerk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Userland PPP fails to load via rc.conf (7.2/amd64) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 11:49:49 -0000 Hi Ruben, Output is as follows: /usr/bin/su: libutil.so.7 => /lib/libutil.so.7 (0x800635000) libpam.so.4 => /usr/lib/libpam.so.4 (0x800744000) libbsm.so.2 => /usr/lib/libbsm.so.2 (0x80084c000) libc.so.7 => /lib/libc.so.7 (0x800962000) Ruben de Groot wrote: > On Fri, Aug 14, 2009 at 06:20:00PM +1000, Alex R typed: > >> Hi Guys, >> >> I ran into the same problem as this person did (see the link below): >> >> http://www.mail-archive.com/freebsd-net@freebsd.org/msg24337.html >> >> ppp starts fine if invoked from shell prompt, however the problem above >> occurs for me when I attempt to start it automatically at boot via >> /etc/rc.conf >> >> Funnily enough, the solution presented in that article seems to fix the >> issue.. But why? This problem is very easy to reproduce, how could it >> have been overlooked? I just happened to find the article in the link >> above, out of desperation, it's not good that I had to Google for a >> solution. >> > > What's the output of the command > > ldd `which su` > > ? > > >> Is the solution given "safe"? Should I open a PR? >> >> Alex >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >> > >