On 9/29/22 00:15, Eduard Bloch wrote:
[*] _LARGEFILE_SOURCE or _FILE_OFFSET_BITS=64
Both of them? I don't think so. _LARGEFILE_SOURCE will export some XYZo
functions of the C API, but I don't use them.
Ok.
apt-cacher-ng has been adding those defines since
the early days of its
Hallo,
* Helge Deller [Wed, Sep 28 2022, 10:12:52PM]:
> On 9/28/22 21:52, Eduard Bloch wrote:
> If you call readdir() a few lines below, this readdir will not be able
> to store the file info in the dirent struct (if the file is located in
> high area of discs), instead returns NULL with errno
On 9/28/22 22:12, Helge Deller wrote:
The problem here is, that if those flags [*] aren't set, the "struct dirent"
will only be able to hold file numbers which are max. 32bits width.
"File numbers" is wrong... I meant "Inode number" (of the file).
Helge
On 9/28/22 21:52, Eduard Bloch wrote:
Hallo,
Hallo Eduard,
* Helge Deller [Wed, Sep 28 2022, 12:46:53PM]:
Package: apt-cacher-ng
Severity: 3.7.4-1
Tags: lfs, hppa, patch
Please enable large file support.
apt-cacher-ng uses readdir() which can fail on 32-bit arches
running on large discs.
Hallo,
* Helge Deller [Wed, Sep 28 2022, 12:46:53PM]:
> Package: apt-cacher-ng
> Severity: 3.7.4-1
> Tags: lfs, hppa, patch
>
> Please enable large file support.
> apt-cacher-ng uses readdir() which can fail on 32-bit arches
> running on large discs.
This does not make sense. readdir() does not
Package: apt-cacher-ng
Severity: 3.7.4-1
Tags: lfs, hppa, patch
Please enable large file support.
apt-cacher-ng uses readdir() which can fail on 32-bit arches
running on large discs.
Sometimes I see a cron job warning:
/etc/cron.daily/apt-cacher-ng:
Aborted
run-parts:
6 matches
Mail list logo
