Also, you have like 4 replies to my comment and they're all made at roughly the same time and 2 are identical. How do you even do that? Please don't spam
> We've run services like that for decades but that doesn't mean there aren't problems with it.
True. But at the same time this also doesn't mean that multiplying tmps are going to solve those problems while not introducing quite a lot of others.
> you have like 4 replies to my comment
I did that as a courtesy to readers and you so that we can have different disagreements on different topics that you have covered in the original comment.
If anything, I'd say that /tmp is more of a hacky solution than private tmps. Private temps is really just allowing you to force a program to perform to use mktemp rather than rely on /tmp. Much easier to provide that "patch" than to get a maintainer to modify what they're doing.
I agree that it is a more powerful tool than is needed to solve the actual problem, but a lot of times you don't actually have the power to solve the root problem (or solve it and keep it solved). So the solution works out pretty well imo.
I'm open to better solutions but you've only made complaints and offered no alternatives. Maybe you have better solutions, but who's going to know what they are and how are we going to know they're better if you make us guess? It's also why I'm not going to "fight" back because there's not a point when there's no real opposition. I wouldn't even know what I'm "fighting against" other than "the way status quo" which has obvious errors and is why this tooling was created in the first place. But please, I honestly do want to hear better solutions so I can make effective use of them.
Pretty much no service should use that. We have ran services without that for decades until LP crowd came and said we should.