|
On Mon, Aug 8, 2016 at 4:16 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:
I'll say this: If /tmp is the right place to put persistent, required
components, then my intuition for this stuff is even worse than I
thought!
With this I agree, but I don't believe that would be the case. I had a
private email from someone stating that /tmp for linux is "normally" just
that... temporary. And that the application "should" remove stuff from it
once done.
Maybe just an over site on the port of NodeJs or something else. My
software uses /tmp for the default temporary directory and I've seen cases
where if someone runs our application it will be able to create files in
this directory but not remove them, because of some authority issues.
I will probably just delete them (or move them...) and see if things
break. If they do... *ugh*.
Brad
www.bvstools.com\
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.