Metrics missing

Posted Jun 5, 2024 12:56 UTC (Wed) by bluca (subscriber, #118303)
In reply to: Metrics missing by koh
Parent article: Debian's /tmpest in a teapot

> I can't change defaults on rented servers not under my control. So there's that problem with defaults.

Fortunately for your use case, as per documentation, your program can just take an flock on the file(s) it is using, and they will be skipped over, no need to change configuration. Also, it's not just ctime, but mtime and atime too that are taken into account for the aging algorithm, again as documented. So it doesn't matter when the file was created, if it was just accessed it will be left where it is.

Metrics missing

Posted Jun 5, 2024 13:02 UTC (Wed) by koh (subscriber, #101482) [Link] (1 responses)

Many thanks for pointing me to flock. I can probably use that Linux-specific hack. The reason I'm regarding this as a hack is that for no other OS known to me it is necessary to take measures to ensure that tmp-files created by a program stay there as long as the program is running.

Metrics missing

Posted Jun 5, 2024 13:22 UTC (Wed) by daroc (editor, #160859) [Link]

A) I'm glad you learned about flock.

B) Jon asked for a very similar thread (back and forth without anyone changing their position, covering many of the same points, including flock coming up) to stop yesterday. We're all smart people here; I am certain that we can all generalize. I don't think anything new is being said, which means we can stop here.

Metrics missing

Posted Jun 5, 2024 14:10 UTC (Wed) by smurf (subscriber, #17840) [Link]

> and atime too

Thus /tmp-on-RAM should arguably work *better* than /tmp-on-root-with-no-or-rel-atime-option, which has been the default for ages.