On 02/23/2015 12:27 PM, Yamaban wrote:
Both of these have the "PrivateTmp=yes" setting, but I have never seen these two services use any tmpfiles at all.
I haven't looked at the code but ... It is a well established technique dating all the way back in my experience to UNIX V6 of 1970s vintage to have a process open a file (often in /tmp) and then delete it. So long as the process or its children has an open file handle for that file it exists and is usable by the process or its children, even for interprocess communication & signalling. When the last processing holding a file handle for this file closes the handle or exits the file vanishes. Perhaps those processes use this technique. As I say, I haven't looked at the source. Either way, this raises the question about systemd leaving such debris in /tmp. Hmm. It seems a few other things like acroread and Mozilla do too. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org