New files filling up /tmp: stdInFifo, stdOutFifo, stdErrFifo
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
New files filling up /tmp: stdInFifo, stdOutFifo, stdErrFifo
After the Great vtown-->current/kde Rollout of Aught-Twenty, new files are accumulating in /tmp. Like Thunderbird's /tmp/ns*, a bad-form design flaw somewhere fails to clean up its temporary files in their class destructor. So far,
stdInFifo5NL
stdInFifoK3h
stdInFifobmp
stdInFifoyXg
with their matching stdOut and stdErr cohorts are accumulating, never purged. which new package is generating them and why aren't they ever deleted sans sysadmin intervention?
They are all zero-length file type 'p' - named pipes.
Last edited by hpfeil; 12-09-2020 at 10:13 AM.
Reason: ls -l
Gotcha! Kate is the culprit. Lsof shows lots of plumbing going on, so I started with a fresh reboot, launched the usual suspects one at a time watching /tmp. The 3 named pipes appeared only after I launched kate. Since I may open and close kate many times during the day, and kate does not clean up after itself, the defunct pipes accumulate with with three random letters as their suffix. I thank everyone who offered assistance in this matter.
I'm not convinced these named pipes come from Kate, although they do appear upon launch. I can't find any instance of QQueue or any other named pipes in the Kate git sources. This happens on only my Ryzen box, not an A6 laptop.
Thank you, RadicalDreamer!
I use rsync to mirror slackware64, then `upgradepkg --install-new`, so I'm not sure this is a missing dependency issue. I may have done the rsync during the mirror updates, so will try that again. Just a local mystery, nothing for the Kate developers to hassle over.
Issue isolated to something in ~/.local. Named pipes no longer appear with a blank .local. I'm interested to know which setting caused this, but I'm closing this as a personal mystery. I appreciate your helpful suggestions!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.