Quoting =?UTF-8?B?VmVkcmFuIEZ1cmHEjQ==?= <[EMAIL PROTECTED]>: > Same here, except I can't login[1] even using sash. > > If I start nscd, login, and then disable nscd, sash will work (unlike bash > or zsh). > > [1] Authentication is, actually, successful, I see the MOTD, but shell > isn't started and it brings me back to "login: ".
Maybe the latest libnss-ldap is more picky about exit/return codes OR messages produced by the shell? I know that I have problems with ssh/scp if I have a verbose .bashrc! If my .bashrc is outputting text, and i try to scp a file to that machine (with the verbose .bashrc), then the scp will fail! Disabling the output, and all is well... Maybe something similar with the latest libnss-ldap? Just an idea... -- CIA Rule Psix explosion PLO Khaddafi Legion of Doom Soviet class struggle Panama ammonium toluene security bomb president KGB [See http://www.aclu.org/echelonwatch/index.html for more about this] [Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf] If neither of these works, try http://www.aclu.org and search for echelon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
