Am Samstag, den 27.02.2016, 23:59 +0100 schrieb Aurelien Jarno:
> On 2016-02-26 22:03, Fabian Niepelt wrote:
> >
> > >
> > > IMHO making sure that programs are restarted after applying the
> > > security
> > > update should be enough, but I
> IMHO making sure that programs are restarted after applying the security
> update should be enough, but I am not fully sure about my analysis, so a
> confirmation would be nice to have.
The machines in question have been rebooted a few times after upgrading.
I will try to get a full backtrace
This is the correct output, the older one contains a test I thought was
in an endless loop but succeeded after a few minutes.
Greetingsroot@linux-6sir:~/glibc_tests > ./bug18665-tcp
info: old timeout value: 1
info: old retry attempt value: 4
info: old _res.options: 0x802c1
info: old _res.nscount
Am Freitag, den 26.02.2016, 05:01 -0500 schrieb Carlos O'Donell:
> On Fri, Feb 26, 2016 at 3:57 AM, Fabian Niepelt <F.Niepelt@mittwald.d
> e> wrote:
> >
> > I'll be gladly providing additional info if you require it.
> > Program received signal SIGSEGV, Segmentation
Package: libc6
Version: 2.13-38+deb7u10
Dear maintainer,
since the latest update for glibc we keep observing occasional
segmentation faults in libresolv [1]. They are triggered (for us) by
php5-fpm which runs an Owncloud instance when logging in. After the
segfault happens, I can relogin
Package: gdisk
Version: 0.8.5-1
I am trying to create 3 partitions on a 7.5 TiB RAID60 device (/dev/sda,
handed to the OS by a hardware raid controller).
Status before:
---
% sgdisk -p /dev/sda
Creating new GPT entries.
Disk /dev/sda: 16002748592 sectors, 7.5 TiB
Logical sector size: 512 bytes
6 matches
Mail list logo
