source of /tmp/{portage,screen} directories? [in progress]

[CaptainBlood]

openrc here:

[Goverp]

In my case, yours may differ, it's the result of running "screen" on a tty to get scrollback.
_________________
Greybeard

[CaptainBlood]

Indeed, when rebooting after app-misc/screen package removal, this directory isn't created anymore...
Now the new question is how is it created?
I don't recall have set something in this regard....

As coming back to OP, the same question for /tmp/portage...
How is it created?

I may be the cause of all of this, albeit not remembering some details.
However I don't like the feeling something is happening in my back.

I really would like to know how this all happens...

Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "

[gentoo_ram]

The /tmp/screen directory is created when someone or something runs the 'screen' command. If you don't clear your /tmp directory at boot (and my set up does not) then what it means is that something ran the 'screen' command at some point.

[pingtoo]

[flexibeast]

`tmp` directories are for temporary files that programs create, for various reasons, in order to do their job. It's a standard programming technique (e.g. in the blogging software i've written for my own use).

For example, when creating a file with certain contents at the user's request, a program might create a temporary file for output, only renaming that temporary file to the intended file name if the output operation was entirely successful. This avoids creating a file that doesn't contain all the intended content, which might be an issue if other programs are assuming that such a file will necessarily contain such content.

There are programs to help you determine which programs are working with certain directories and files, such as fuser(1) and lsof(8).

In the case of screen(1) in particular, the README file talks about the use of `/tmp/screen-exchange` for writing and reading the copy buffer, and the INSTALL file mentions that the `/tmp` directory can be used to create sockets when multiple users are using screen. But i can't immediately see any reference to `/tmp/screen` in the source (which might simply because that path is created on the fly, rather than being a literal).

If the creation of temporary files is a general concern for you, you should certainly become familiar with something like fuser(1), and with grep'ing the source code of the relevant program to learn why a given temporary file is being created, and for what purpose.

[gentoo_ram]

The /tmp/screen string is definitely in the executable:

[flexibeast]

[pa4wdh]

On my system the /tmp/screen directory is created by a tmpfiles.d entry added by the app-misc/screen package:

[Goverp]

From the screen ebuild - verbatim:

[CaptainBlood]

Very nice clarifications what's happening there.

[sam_]

You can write your own snippet and/or use INSTALL_MASK if it bothers you.

For Portage, it exists for a good reason (because of privilege escalation issues).

[CaptainBlood]

[CaptainBlood]

[Zucca]

[CaptainBlood]

Here is:

[CaptainBlood]

[Zucca]

[Goverp]