Skip to content

Conversation

@jgh9
Copy link

@jgh9 jgh9 commented Apr 28, 2017

Writing to /tmp on many systems these days is a ram filesystem and using this location could cause system issues if it is a large repository.

CNG and others added 7 commits April 19, 2017 00:41
@CNG
Copy link
Owner

CNG commented May 14, 2017

I need to research this more. I thought /var/tmp is not cleared out by the system on any schedule or ever (perhaps this is is just for certain OSes or I might be wrong), and if that's true, the script probably needs to be more robust to make sure files aren't left in the case of premature exit. In general there are various ways of doing temp files throughout the repo and I should also make those consistent.

@jgh9
Copy link
Author

jgh9 commented Jun 9, 2017

/var/tmp is sustained through reboots, but this area is usually considered a scratch space. /tmp is now normally a tmpfs system. In my humble opinion, using /var/tmp with some error checking is a more favorable approach over using /tmp that would more than likely these days eat into physical RAM of system. Thanks for the updates!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants