Blog: 2023-12-27: Difference between revisions
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
I think for now I'm just going to put the pidfile in ~/.ronin, we'll see how far that gets me. |
I think for now I'm just going to put the pidfile in ~/.ronin, we'll see how far that gets me. |
||
Also while I work on making ronin more user friendly, I should document its basic functionality so that I can compare the qemu implementation with a podman one (which I might call roman). |
|||
Revision as of 01:09, 27 December 2023
Ok struggling with basic pid kinda stuff for a `ronin status`
https://serverfault.com/questions/159334/what-permissions-are-needed-to-write-a-pid-file-in-var-run
means I can't do a pid in /var/run I guess, unless I create it during the apt install... I guess...
More discussion of alternate pid file locations: https://superuser.com/questions/454449/linux-alternative-places-where-to-store-pid-file-instead-of-var-run
Maybe I should be using virsh to launch qemu, and that would give me an easy way to manage the status?
Yet more pid discussion https://superuser.com/questions/238412/write-a-pid-file-manually-from-bash-script
I think for now I'm just going to put the pidfile in ~/.ronin, we'll see how far that gets me.
Also while I work on making ronin more user friendly, I should document its basic functionality so that I can compare the qemu implementation with a podman one (which I might call roman).