added section about managed memory dumping #1099
Conversation
|
I don't think the |
|
This should be under testing, contributing or troubleshooting |
|
What I meant was make troubleshooting a category and put memory dumps under it |
|
@JPVenson do I have your permission to make the changes related to categories and commit them directly to this branch? |
Cloudflare Pages deployment
|
| Run this command to determine the PID of the Jellyfin server: | ||
|
|
||
| ```sh | ||
| ps aux | ||
| ``` | ||
|
|
||
| The above command will display a list of processes similar to the following: | ||
|
|
||
| ```cmd | ||
| # ps aux | ||
| USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND | ||
| root 1 1.8 7.4 276905428 2304952 ? Ssl Sep04 17:23 /jellyfin/jellyfin | ||
| root 914 0.0 0.0 2480 580 pts/0 Ss 05:33 0:00 sh | ||
| root 2171 0.0 0.0 6756 2940 pts/0 R+ 12:55 0:00 ps aux | ||
| ``` |
There was a problem hiding this comment.
maybe just ps aux | grep /jellyfin ?
There was a problem hiding this comment.
that would not work for any process running actually barebones. I dont have a barebones install so /jellyfin/jellyfin is actually the path docker uses.
There was a problem hiding this comment.
Why not? Isn't ps aux | grep /jellyfin just feeding the output of ps aux to find lines that contain /jellyfin? In the docs you suggested that the right most part of the command will always be /jellyfin
Added page how to create a memory dump with dotMemory for Linux and Windows