Steve Crosby wrote: > > > That particular issue was with shadow-4.0.8 and was a direct result of > coding error - there is a big comment in the definitions for login.defs > that entries must be in alphabetical order, and the developers ignored it > during some 4.0.8 changes related to PAM. > > 4.0.9 fixes the problem (by changing the search algo to be sequential, > instead of binary) - so you should *not* see these errors in shadow 4.0.9 > (I certainly no longer see them here). > > - -- > Steve Crosby
Steve, you do not have problems, but others do following BLFS instructions. Unless I'm just way off base. I see two issues here. I would just like to clarify having not dealt with it myself yet. 1: All of those defines should be commented out in shadow-4.0.9/etc/login.defs.linux. Did shadow update that file in 4.0.9/10 as suggested should have been done, and you copied it? Or was it manually done in /etc/login.defs by you? 2: The coding issues and alphabetical order...by chance got a BZ link for that? I haven't seen anything, but haven't really looked either. Not that I doubt you at all, I just haven't seen it yet and feel a little week on the topic. Esp with the quick releases lately. If not, I'll look tomorrow night. For those still seeing the problem, by only my half informed knowledge, it looks as if you should simply comment out the problem lines in /etc/login.defs as these are handled by PAM, not shadow...or possibly copy the login.defs.linux provided in the shadow build tree. I don't know yet if this is dynamically generated or not however. Definately make a backup copy first, and have a rescue disk ready. Thanks. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
