[Citadel Development] Re: Write server PID to citadel.lock in addition to locking it.
Whoa, what font is that ?!! I am aware that `/var/run` is the conventional location, and may yet move it there. Doing so would, however, prevent multiple instances of Citadel Server from running on the same host. There were definitely people doing that in the past, but I wonder if nowadays that is still a thing, with everyone now having virtual machines and jails and containers and all sorts of other ways to isolate multiple workloads on the same machine.
[Citadel Development] Re: Write server PID to citadel.lock in addition to locking it.
PID files are usually in /var/run and are suffixed with "pid" as seen in the attached screenshot of my /var/run Mon Sep 18 2023 10:21:10 EDT from rss <> Subject: Write server PID to citadel.lock in addition to locking it. This will be useful for systems like FreeBSD that need to know a PID to monitor.
[Citadel Development] (null)
Quick update regarding GitLab and git itself: I've removed SSH access to the repository. All access should be through HTTPS. This is much more secure. And yes, you can store your creds. The recommended procedure if you plan to commit is to grab yourself a Personal Access Token using your profile, and then use that as your password. You can edit .git/config and set up your creds like this: https://username:to...@code.citadel.org/etc/etc/etc This gives you the ability to commit without typing in your password every time, but without having to store your cleartext password on your dev machine. And of course you can revoke the token at any time. Share And Enjoy
[Citadel Development] removed some verbage, but really a git test
[Citadel Development] Additional memory allocated since startup: %d bytes message now identical to ...
[Citadel Development] Write server PID to citadel.lock in addition to locking it.
This will be useful for systems like FreeBSD that need to know a PID to monitor.
