On Jul 22, 2024, at 08:08, [email protected] wrote:
I found that after I rebooted the system, the dir /var/run/*** disappeared.
I put my app's web sessions under /var/run. so they got lost.
Is there an effective tool to manage /var/run dirs?
Thank you
--
corey hickman
The contents of /run (which /var/run points to) are temporary.
I found that after I rebooted the system, the dir /var/run/*** disappeared.
I put my app's web sessions under /var/run. so they got lost.
Is there an effective tool to manage /var/run dirs?
On Jul 22, 2024, at 08:08, [email protected] wrote:
I found that after I rebooted the system, the dir /var/run/*** disappeared.
Yes,
/var/run
is a symlink to /run
And /run is a tmpfs
I put my app's web sessions under /var/run. so they got lost.
Well that was a bad idea if you wanted to have persistent session ids.
Is there an effective tool to manage /var/run dirs?
Thank you
--
corey hickman
Would it be appropriate to use the /opt directory?
I found that after I rebooted the system, the dir /var/run/***
disappeared.
I put my app's web sessions under /var/run. so they got lost.
Is there an effective tool to manage /var/run dirs?
For coreyh, here is the link to Linux Filesystem Hierarchy, v3: <https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf>. And here
is Wikipedia's page digesting it: <https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard>. The
documents discuss where various bits should go, including 11 pieces
for various /var locations.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 146:12:44 |
| Calls: | 12,089 |
| Calls today: | 2 |
| Files: | 15,000 |
| Messages: | 6,517,501 |