×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Vern,
Am 27.02.2024 um 23:32 schrieb VERNON HAMBERG Owner via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:
Interesting, I know I have had no idea why to use /var - and now that I looked it up, one description is it holds files that change in size. A further search says we shouldn't use it at all, it's outdated.
Um. May I ask for some reference about /var being "outdated"? From experience, it's not.
/var IMHO is comparable to the QUSRSYS library on IBM i. It holds "variable" data, such as spool (mail, print) and log files, and is most often used by application packages. Another way to look at it is "a home directory for system wide applications".
The biggest difference between /var and /tmp is that /tmp is considered volatile between reboots, while things in /var are meant to stay unless deleted manually. In fact, some directory structures in /var on Linux are required and may break applications if deleted for "cleanup purposes".
As others stated, cleaning /tmp in restricted state or even automatically in QSTRUP is usually safe, unless you have applications requiring intermediate data to continue processing. But then, /tmp would have been the wrong spot to put that data there in the first place. :-)
:wq! PoC
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.
midrange.com
