configuration file

[dun]

A configuration file is becoming increasingly necessary:

• supporting multiple keys (#⁠19)
• specifying the origin IP address of a network interface (#⁠23)
• suppressing log messages for non-existent users (#⁠26)
• specifying the minimum syslog level of messages to log (#⁠26)
• overriding several compile-time paths at runtime using long options (#⁠57)
• specifying the number of worker threads ("num-threads") (#⁠64)
• disabling cryptographic algorithms deemed insecure (#⁠73)
• specifying allowed UIDs/GIDs for encoding/decoding credentials with a given key (#⁠104)
• specifying the key file location (#⁠129)
• specifying the "listen-backlog" limit for the socket (#⁠139)

[borkd]

Is override with long options the best way to get spack-built munge et al to work?
chaos/diod#38

[dun]

The MUNGE client (libmunge) and server (munged) communicate over a Unix domain socket. The default path of this socket is configured at compile-time [$(localstatedir)/run/munge/munge.socket.2].

munged creates this socket each time the daemon is started; its default path can be overridden with the --socket option. libmunge can override it via munge_ctx_set(). But the path specified via munged --socket has no effect on the path used by libmunge.

I'm not familiar with spackification, and I'm not sure how you have things configured. Maybe you're running the system-installed munged which is listening on /var/run/munge/munge.socket.2, and diod is linked against a spack-built libmunge that has been configured with a different path. If you're just needing to override the default path for this socket in your spack-built libmunge, there's (currently) no configure option to do that (but it would be straightforward to add); instead, you'd have to modify MUNGE_SOCKET_NAME in src/libcommon/munge_defs.h.

Update: Commit 565db69 adds the --with-munge-socket=PATH configure option.