-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache management #40
Comments
So, every-time we run recon or project, we should 'touch' the sysmatrix file? |
Yes, that way its time stamp will update. |
We can just do it in one place, under the line that prints "Found system matrix". Not sure "touch" will work in Windows though unless it's run in a bash emulator. |
There's a useful discussion here on how to implement |
Yes! This works for me on Linux,Mac,Windows: The above is all we need here because we just need to update the modified time for a file that exists. |
OK, we have added a After some thought, maybe it would be best to create a separate utility Do people like this idea? |
Sounds good. There's already a function _clear_cache() that could be modified. I'd suggest having it default to cleaning the cache folder entirely. Like We should take care to identify the specified path as a valid cache folder so it can't be used to obliterate an arbitrary folder. |
We should implement a function
Then if the user responds with a |
Brendts suggestion: Perhaps allow the user to specify a maximum cache size? If writing a |
Add functions to "list" and "clear" sysmatrix files from cache directory.
We should use "touch" or something equivalent to update the time stamp of the sysmatrix file each time it's accessed in order to assigning priority.
The text was updated successfully, but these errors were encountered: