http://qa.mandrakesoft.com/show_bug.cgi?id=2546
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From [EMAIL PROTECTED] 2003-03-09 22:37 -------
Thank you kindly for your efforts and I apologize for the delay in response...it
was a very hectic week.
The libc.so.6 that you posted does work correctly with the VPN client. I will
forward your suggestions to the developers and hope that they can fix this.
Thanks again.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
With -10mdk, my VPN client that IBM provides was broken. Apparently there is a
bug/feature in 2.3.1 that caused this.
Here is a transcript of a work-around for this problem:
-----------------------------------------------------------------------------
I figured out how to get around the glibc 2.3 (used in debian unstable) problem.
The problem is that attvpnctl is core dumping with a segfault. It's the result
of statically linking to a library that dynamically loads shared libraries to do
name resolution. (Why is it statically linked!?!)
Anyway, the fix is to:
1) edit attvpnctl with emacs.
2) search for /etc/nsswitch.conf and change to /etc/nsswitc-.conf.
3) save and exit from emacs. THE FILE SIZE SHOULD NOT HAVE CHANGED!
4) now copy /etc/nsswitch.conf to /etc/nsswitc-.conf
5) edit /etc/nsswitc-.conf change the line
hosts: files dns
to
hosts: dnsnoexist
Yes, dnsnoexist is invalid, but that is the point, we can't load anything! Any
shared library is going to segfault!
Now your good to go!
-----------------------------------------------------------------------------
I am also able to work around it using LD_LIBARARY_PATH set to a directory
containing the library binaries from the -6mdk version.
I'm not sure if this is what was fixed or not, but this is the closest I can
find in their tracking system:
http://bugs.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=glibc&pr=4744
Someone told me that Slackware has incorporated a fix into their glibc which
fixed the problem.
I'm hoping that someone can find the patch and incorporate it into Mandrake's
glibc. I checked the glibc-cvs list archives, but they apparently don't include
the patches in the archive.
