Hallo Mark,

yes, indeed, disk_usage_limit triggered this. 

best regards,
coldtobi

Am Sonntag, den 30.09.2012, 13:36 +0100 schrieb Mark Hindley:
> On Sun, Sep 30, 2012 at 01:14:04PM +0200, Tobias Frost wrote:
> > Package: apt-cacher
> > Version: 1.7.5
> > Severity: normal
> 
> Actually, I think I have found this. Do you have disk_usge_limit 
> configured?
> 
> I think this patch fixes it:
> 
> 
> diff --git a/apt-cacher b/apt-cacher
> index 6e5bd47..b3863aa 100755
> --- a/apt-cacher
> +++ b/apt-cacher
> @@ -1644,7 +1644,8 @@ sub libcurl {
>                           if (defined($statfs = df($cfg->{'cache_dir'}, 1)) &&
>                               $response->header('Content-Length') &&
>                               $response->header('Content-Length') >=  
> $statfs->{bavail} ||
> -                             $cfg->{_disk_usage_limit} && $statfs->{used} + 
> $response->header >= $cfg->{_disk_usage_limit}) {
> +                             $cfg->{_disk_usage_limit} &&
> +                             $statfs->{used} + 
> $response->header('Content-Length') >= $cfg->{_disk_usage_limit}) {
>                               info_message('ALARM: Insuffient space for 
> Content-Length: '.
>                                            
> $response->header('Content-Length').
>                                            ' in cache_dir with ' . 
> $statfs->{bavail} . ' available space');


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to