Best way to handle small interactive workloads on almalinux?

Hi all,
I’m experimenting with AlmaLinux for everyday use and testing how it handles small, interactive workloads alongside normal services. One thing I’ve noticed is that repeated sessions sometimes leave behind temporary files or processes that aren’t always obvious at first.

While checking a simple word-based project to learn more about it made me wonder how others manage cleanup and resource tracking on AlmaLinux. Do you rely more on system tools, periodic scripts, or containerized setups to keep things tidy?

Would be great to hear how others approach this in real-world environments.

Hello.

For temporary files, I generally rely on the OS-standard systemd-tmpfiles.
If you want to periodically clear specific temporary directories, I think the most reliable approach is to write rules in /etc/tmpfiles.d/*.conf and manage them that way.

For process/resource monitoring, I primarily use the following:

systemd-cgtop, systemd-cgls (for cgroup visibility)
ps -eo pid,ppid,stat,cmd (for PID/parent-child relationship verification)

For virtualization, I use KVM; for containers, I use LXD.
For testing where I don’t want to dirty the host, I often lean towards running things on the LXD side.

thanks