Hi Alfred,

On 7/19/22 09:26, Alfred M. Szmidt wrote:
    > I think the first question is to understand what a "library state
    > directory" is?  Whate are you storing under it?  Seems like something
    > architecture independent? Are the files shareable between
    > installations?

    I'm talking about NGINX Unit, which stores the running configuration
    (kind of what /etc/nginx/nginx.conf was to NGINX, but Unit uses a
    runtime defined JSON file).  It also stores a few other files, but
    that's the main one.  If the process is restarted, it picks up that
    configuration, so it needs to be kept after reboot (so not /run)

That sounds like a cache file, so why not /var/cache?  I don't
understand why /var/lib though ...

Hmm, it wouldn't be completely unreasonable to use /var/cache.

But since the file doesn't represent a cache of the state, but the actual state (modifying the file would modify the state of the program).

Since /var/lib is "variable state information" (according to FHS 3.0), I think it makes more sense, but I'm not sure about it. I've never used it before.

    It is arch independent.

    And it doesn't make sense to share it, as it represents the state of the
    running instance of unitd.  Sharing it would probably break other
    instances of the process when one of the instances modifies it.

Ok, then something under /var would make sense.



Alejandro Colomar

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to