** Reply to note from Michael Lake <[EMAIL PROTECTED]> Wed, 10 Sep 2003 11:50:01 +1000
> I wonder if it could be some library that passwd uses that is corrupt?
> running ldd /usr/sbin/passwd
# ldd /usr/bin/passwd
libuser.so.1 => /usr/lib/libuser.so.1 (0x40023000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40036000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x40063000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x4009c000)
libdl.so.2 => /lib/libdl.so.2 (0x400a0000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x400a3000)
libpam.so.0 => /lib/libpam.so.0 (0x40108000)
libpam_misc.so.0 => /lib/libpam_misc.so.0 (0x40111000)
libpopt.so.0 => /usr/lib/libpopt.so.0 (0x40114000)
libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
so far I've replaced /lib/security/pam_stack.so
> (or what ever is that path to passwd) would show what libs are being
> used by that and maybe reinstalling some would not hurt. Surely a pam
> config file error should not cause paswd to segfault but a lib that pam
> uses might cause it if its faulty.
>
> What was the alst thing that was upgraded or changed on your system?
Postfix, BUT, the 'passwd' has been broken for a while now
Voytek Eymont
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
