4 ms·
Only on my personal machine. If I’m logged in elsewhere and keep my habit of working on large files in /tmp, I will be in for a bad surprise
by pantalaimon 2y ago
Only on my personal machine. If I’m logged in elsewhere and keep my habit of working on large files in /tmp, I will be in for a bad surprise
- stouset 2y agoSo… don’t keep large files you want to control the lifecycle of in directories you don’t own? If you care about it, stop putting it in /tmp. You were always setting yourself up for a bad surprise by doing this, and now you’re surprised?
- pantalaimon 2y agoI might download an ISO or check out a repo I want to build just once. Or copy some (large) files there because I run a script on them and persevere the original in case something goes wrong. I don’t care about those files once I’m done with them - so far they would only be gone with a reboot, which aligns well with my definition of done.
- yjftsjthsd-h 2y agoIf you really don't want to delete manually you can just `sudo mount -t tmpfs ~/tmp` or so
- stouset 2y agoIf you’re downloading large files (so large you’re concerned about an in-memory tmpfs) to boxes that you don’t own, stop just leaving them around in the first place. Sure, /tmp is cleaned on boot. But if the host is rarely rebooted it’s pretty inconsiderate to just leave enormous quantities of unneeded crap lying around in shared directories. /tmp isn’t supposed to be a garbage dump. It’s supposed to be for data that’s actually in use but transient or relevant to running processes. You’re still expected to be a good citizen on shared hosts and clean up after yourself when you’re done.
- Macha 2y agoThis is true already if your remote machine is red hat, fedora, arch, opensuse, rocky, ...