Userland PPP fails to load via rc.conf (7.2/amd64)

Alex R alex at mailinglist.ahhyes.net
Fri Aug 14 12:22:23 UTC 2009


Thank you Ruben :-) :-)

I wouldn't have thought in a million years that could be the issue, but 
what you have said makes perfect sense. Looks like its back to /bin/sh 
for root.

Cheers, Alex.

Ruben de Groot wrote:
> On Fri, Aug 14, 2009 at 10:08:48PM +1000, Alex R typed:
>   
>> Actually I did change the root shell to bash. U think that might cause it?
>>     
>  
> Definately. before ldconfig is run, only the system libraries in /lib and /usr/lib
> are known. Doing a "su -m root" at that time, as /etc/rc.d/ppp is doing, will
> result in the error message you got, as bash wants to load libintl.so.8, which
> lives in /usr/local/lib.
>
> Ruben
>
>   
>> Ruben de Groot wrote:
>>     
>>> On Fri, Aug 14, 2009 at 09:49:48PM +1000, Alex R typed:
>>>  
>>>       
>>>> 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)
>>>>    
>>>>         
>>> That's normal. Shall I take a guess?
>>>
>>> You changed root's shell to bash!
>>> bash uses libintl, and will be invoked by the "su -m $ppp_user" in
>>> /etc/rc.d/ppp
>>>
>>> Yet another good reason not to change root's default shell :D
>>>
>>> cheers,
>>> Ruben
>>>
>>>  
>>>       
>>>> 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 at freebsd.org mailing list
>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>>>>> To unsubscribe, send any mail to 
>>>>>> "freebsd-questions-unsubscribe at freebsd.org"
>>>>>>   
>>>>>>        
>>>>>>             
>>>>>      
>>>>>           
>>>> _______________________________________________
>>>> freebsd-questions at freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>>> To unsubscribe, send any mail to 
>>>> "freebsd-questions-unsubscribe at freebsd.org"
>>>>    
>>>>         
>>>  
>>>       
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>>     
>
>   



More information about the freebsd-questions mailing list