News for hackers. Stuff that matters.
Re:Debian's /tmpest in a teapot by dheera on Wednesday June 05, 2024 @01:49AM (#40581758)
> But automatically deleting files - in either of those - while the system is running is going to break all sorts of things.

Detect the process that created a file and delete it 24 hours after the process ends.

Re:Debian's /tmpest in a teapot by jgalt212 on Wednesday June 05, 2024 @07:43AM (#40583739)
Thanks for the homework assignment. The entire value proposition of tmp is there is no homework to do later.
Re:Debian's /tmpest in a teapot by leni536 on Wednesday June 05, 2024 @07:49AM (#40583780)
Chrome is multi-process, isn't it?
Re:Debian's /tmpest in a teapot by blucaz on Wednesday June 05, 2024 @09:37AM (#40584599)
Or what about, delete it after 10 days it was last accessed (regardless of whether for read or write)? Hint: that's already how tmpfiles.d works
Re:Debian's /tmpest in a teapot by o11c on Wednesday June 05, 2024 @12:38PM (#40587075)
That will fail badly with multi-process programs, which includes the example of browsers, and many others (databases anyone?).