|
Well I thought I would indicate that I have tried to eliminate the possibility that some other process on the machine was causing the file-handle equivalent of a memory leak, and also that I have pretty high confidence that the system is, indeed, presenting sufficient file resources to any process running. I'd actually prefer that the issue NOT be DNAS and would be some system-environment related thing that I could sweep away with a setting or a script- to that end I've been trying to examine what's happening on the machine. I am still half convinced that something related to being a virtual Linux instance might actually be the culprit, though damned if I can find out WHAT, exactly.
|