Hi, We've encountered into the same bug (vmalloc leak in afs client when klog many users, openafs-1.4.0-rc4). Is the need to call "sysctl -w afs.GCPAGs=1" - when you don't want memleak - a bug, or it's by design?
On Thursday 28 July 2005 21.41, Chaskiel M Grundman wrote: > --On Thursday, July 28, 2005 10:00:04 AM -0700 Miles Davis > > <[EMAIL PROTECTED]> wrote: > >> you could try enabling pag garbage collection > >> sysctl -w afs.GCPAGs=1 > > > > Huh... I had no idea those were there. The default seems to be 2 -- what > > does that mean, and are these documented somewhere? > > Documentation on new features? hah. > > 2 is AFS_GCPAGS_USERDISABLED > only a value of 1 (AFS_GCPAGS_OK) will cause the garbage collector to run. > I think that the point of the non-zero disable value is because the macro > AFS_GCPAGS is used both as a compile time directive (#if AFS_GCPAGS), but > is also the initializer for the run-time variable afs_gcpags (which is what > the sysctl modifies and affects the runtime behavior of the code when it is > compile-time enabled). There are other possible values for afs_gcpags, > which indicate that the code disabled itself due to encountering an error > while examining process lists. -- Peter Somogyi Software Developer, Gamax Ltd. 1114 Budapest, Bartok B. u 15/d Tel.: +36-1-381-0544 e-mail: [EMAIL PROTECTED] _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
