Timeline for What is file descriptor 47 used for?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2024 at 12:25 | history | edited | user10489 | CC BY-SA 4.0 | added 109 characters in body |
| Jan 25, 2024 at 11:23 | comment | added | A.B | @DarkAtom your question: "What is file descriptor 47 used for". You provide yourself the answer: " have already traced the process which initially leaked the descriptor (it is plasmashell which was started by systemd)". This is the answer to the question. You appear to have changed the goal of your question into "Why does a shell keep file descriptors opened?" which is an entirely different question. "Normally a shell shouldn't leave any descriptors" is debatable, not to be assumed as a postulate. | |
| Jan 25, 2024 at 1:32 | history | edited | user10489 | CC BY-SA 4.0 | added 91 characters in body |
| Jan 25, 2024 at 0:59 | comment | added | user10489 | Good call, I'll add that. | |
| Jan 25, 2024 at 0:58 | history | edited | user10489 | CC BY-SA 4.0 | edited body |
| Jan 25, 2024 at 0:57 | comment | added | DarkAtom | Normally a shell shouldn't leave any descriptors (aside the standard 0-2) open to the program it executes. Leaking descriptors like this can be a security problem if it wasn't done intentionally. I have already traced the process which initially leaked the descriptor (it is plasmashell which was started by systemd), so that isn't a problem. | |
| Jan 25, 2024 at 0:57 | history | edited | user10489 | CC BY-SA 4.0 | added 74 characters in body |
| Jan 25, 2024 at 0:51 | history | answered | user10489 | CC BY-SA 4.0 |