Linux

48315 readers

1373 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Logging: How can I discover what process had ran under a PID, if the process was killed? (feddit.uk)

submitted 1 month ago by theshatterstone54@feddit.uk to c/linux@lemmy.ml

3 comments fedilink hide all child comments

More specifically,

How can I discover what process had ran under a PID, if the process ran under a graphical session which restarted because of a crash, and then I killed it (the session)? It's not in the session's logs (it was COSMIC, so I ran it with RUST_BACKTRACE=1 and redirected the output to a file; nothing, other than a PID for a process that's no longer there).

The error in the COSMIC logs was "PID 22842 does not belong to any known session". I have reason to believe the process is a foot terminal launched by a systemd user service, which ran a script that launched the terminal(s). But I need to be sure, so I know what I'm dealing with, and I can approach it the right way.

Any help, info, or pointers would be greatly appreciated. Thank you.

you are viewing a single comment's thread
view the rest of the comments

[–] graycube@lemmy.world 3 points 1 month ago

There are some monitoring tools which take a snapshot of the process table every few minutes. If you happen to run one of those, and your process happens to be running when the snapshots is taken you can catch it.

If this is a postgresql server and you have logging turned up with pids being logged, and the pin in question was a database process, you can probably find it in the database logs.