J
Justin L Hudson
Here is my issue. I am running a system that will cycle through files
replacing the oldest with the newest. My RAM overlay will fill up to the
point it crashes and it seems to keep growing after the cycle starts over.
Example being; I have a file called "exception1.log", I will delete this
file and write a new one with the same name. When this happens the RAM
overlay space gets bigger (less space). Shouldn't the overlay let go of the
file being replaced? Because if I was to commit the changes it would keep
the last file I change not the ones before it?
Thanks,
Justin
replacing the oldest with the newest. My RAM overlay will fill up to the
point it crashes and it seems to keep growing after the cycle starts over.
Example being; I have a file called "exception1.log", I will delete this
file and write a new one with the same name. When this happens the RAM
overlay space gets bigger (less space). Shouldn't the overlay let go of the
file being replaced? Because if I was to commit the changes it would keep
the last file I change not the ones before it?
Thanks,
Justin