On Sun, Dec 09, 2007 at 01:03:01PM +0100, Pierre Habouzit wrote: > > I manually installed glibc 2.7-4 (libc6_2.7-4_i386.deb) and will reboot > > after > > the backup is finished. > No that won't work you have to go back to a 2.6 one.
I'm restoring a backup. When everything is fixed I'll update my Debian 4.0 testing distribution when my VPS host kernel is compatible with glibc 2.7-4 or later. > > Is there anything else I can check to find out what happened? > The kernel you run on has a custom redhat patch that conflicts with > the new O_CLOEXEC feature. Either they change the kernel, or you keep a > pre 2.6. I assume you mean pre 2.7 (being 2.6). According to https://lwn.net/Articles/236843/ the O_CLOEXEC flag appeared in kernel 2.6.23. I called my VPS provider (Strato), and according to the tech guy they use Debian as host OS. I logged a service request to be sure. My 'uname -a' lists: Linux foobar 2.6.9-023stab043.1-smp #1 SMP Mon Mar 5 16:38:22 MSK 2007 i686 GNU/Linux Can anybody help me find the kernel patch I should ask to be installed (I doubt they do that in short time with a big hosting company like Strato). Can anybody tell me how I can make sure my system doesn't get crashed the next time I do 'apt-get upgrade'? Or should the new patch in glibc-4 prevent problems automatically? Regards, Pieter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
