so what I understand from what you wrote:
by sending the log file (STDOUT) to /tmp I am forcing the system to use memory to hold the log file?
Is that correct?
The log file is often larger than the amount of memory which is no longer free (often larger than the system physcial memory)
Log file may be up to 8G
Physical Memory = 4G
Memory "lost" on one run ~ 300M to 2G
But why does the memory stay lost (not free)?
What can I do to get it back?
Shouldn't it be given back when the programme exits and the log file is written to disk (flushed?).
I log in via a Citrix connection over a (relatively) slow link, so I can't have gigabytes spewing out to an xterm. Sending it to a file on /tmp seemed a good way to keep the output for debugging purposes.
Would I be better off sending the STDOUT to a file on the NFS?
That seems like an odd thing if so!
In reply to Re^3: memory not freed after perl exits. Solaris.
by Workplane
in thread memory not freed after perl exits. Solaris.
by Workplane
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |