http://bugzilla.novell.com/show_bug.cgi?id=533249#c7 Jon Nelson <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #7 from Jon Nelson <jnelson-suse@jamponi.net> 2009-11-16 22:14:45 UTC --- This bug is *not* resolved, and appears to have everything to do with '!' vs '*' in /etc/passwd (or /etc/shadow). '!' is used to indicate a *locked* account I turned up the PAM debugging for pam_unix2 and determined that the postgres account is locked. Performing the above tests (adduser testuser, su testuser ls, etc...) still fail. Why is the behavior different in 11.2 versus 11.1? This prevented the postgresql upgrade from working properly. I had to perform the following steps, once I had an idea that it was a locked account problem: 1. pwunconv 2. vipw and change the password for 'postgres' to '*' instead of '!' - the latter indicates that the account is locked. 3. *now* I can start postgres and such. I will open a bug report regarding the passwd (5) manpage. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.