I've done a bit more digging and it appears that this is only happening on RHEL 4.5 with openafs 1.4.4. The GCPAGs item stays at 1 for RHEL 3 machines.
I'm just trying to figure out if this is a problem I need to investigate more, or if it is "normal" behavior and will not adversely affect my servers. On 7/11/07, Nate Gordon <[EMAIL PROTECTED]> wrote:
I'm currently trying to debug some mysterious server crashes and am curious about how the sysctl var afs.GCPAGs works. From what I've gleaned from the archives/code is that GCPAGs = 1 allows the garbage collection of pags, anything else prevents it. Is this correct? Next why would my GCPAGs be set to EPROCWALK and/or how can I do some more debugging to determine the nature of the problem? I've read through the one spot in the source that sets that and it seems that it failed to dig through the process table and mark in use pags. I specifically set it to be 1 when afs starts up, so something is changing it. Thanks in advance, -- -Nathan Gordon If the database server goes down and there is no code to hear it, does it really go down? <esc>:wq<CR>
-- -Nathan Gordon If the database server goes down and there is no code to hear it, does it really go down? <esc>:wq<CR> _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
