On Thu, Dec 09, 2010 at 02:13:20PM +0100, Schoepflin, Markus wrote:
Status update: The system now runs for 9 days with the patched libperl.
No further segmentation faults of apt-cacher have been observed.
Hi Markus,
If you're still using that system, any confirmation that
perl
No further segmentation faults of apt-cacher have been observed up to
now. Looks like the suggested patch does indeed solve the observed
problem.
Markus
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Status update: The system now runs for 9 days with the patched libperl.
No further segmentation faults of apt-cacher have been observed.
Markus
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Niko Tyni wrote:
Markus, if this is reproducible enough for you would you like to test
if the fix works? You could rebuild the perl package yourself with the
patch (it applies cleanly against 5.10.1), or I can provide you the
.debs if you like.
Meanwhile I have built new perl packages
Mark Hindley wrote:
[...]
This must be a problem in the perl engine somewhere rather than
apt-cacher itself. I notice you are using CGI mode which could also
point to the apache perl module as well. A perl script, like
apt-cacher, shouldn't be able to crash the perl engine.
Agreed.
Have
Niko Tyni wrote:
[...]
Markus, if this is reproducible enough for you would you like to test
if the fix works? You could rebuild the perl package yourself with the
patch (it applies cleanly against 5.10.1), or I can provide you the
.debs if you like.
The crash happens about once or twice a
Niko Tyni wrote:
apt-cacher segfaults at random intervals when clients are accessing
the cache.
Is this visible to the clients? I.e. does it cause any actual problem
like incomplete responses?
Forgot about that one...
No, the downloads in apt seem to work without any apparent problem,
at
7 matches
Mail list logo
