DJ Lucas wrote:
> Randy McMurchy wrote:
>
>>ECI wrote these words on 08/04/05 10:04 CST:
>>
>>
>>
>>>I'm using a LFS 5.1.1 with cracklib + pam + shadow. I have recently upgraded
>>>PAM (0.80) and shadow (4.0.10) and cracklib according to the BLFS dev book
>>>and have a problem with su and PATH variable.
>>
>>
>>This issue was recently discovered and a bug has already been entered
>>into the bug tracking system. Currently, there is no known solution
>>other than to use su -.
>>
>
>
> As the bug report shows, add
> 'PATH DEFAULT=/usr/local/bin:/usr/bin:/bin:... OVERIDE=${PATH}' to
> /etc/security/pam_env.conf to create a valid user path. For a default
> root (superuser) path, create a valid /root/.bashrc that contains the
> overidden path desired.
>
BTW, this is exactly why I suggested in one of the threads, something to
the effect of: The explanatory text needs be expanded a little, but
that the links to documentation currently in the book are sufficient. I
think I was wrong regarding 'sufficient'. Unless it's just staring me
smack dab in the face, I don't see a way to set a default SU_PATH in the
old style. I'll add a note to the bug about creating a .bashrc.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
