aboutsummaryrefslogtreecommitdiff
path: root/gmid.1
diff options
context:
space:
mode:
authorOmar Polo <op@omarpolo.com>2021-10-09 21:40:55 +0000
committerOmar Polo <op@omarpolo.com>2021-10-09 21:40:55 +0000
commitf0a01fc742e83b3f4736b5d64af3ab18148afc5a (patch)
treeb0f9e815f8b7692787bc95fa70d896b648095abf /gmid.1
parent5eb3fc905f5e3bd2f2d586fb1e0ceda879500b3e (diff)
two -n to dump the parsed configuration
This adds a barebone dumping of the parsed configuration. It is not complete, but I'm interested in dumping the full path to `cert' and `key' in order to write some scripts that can inspect the configuration, extract the certificates and renew them when expired automatically. It's not easy to parse gmid configuration otherwise because the syntax is flexible and users can use macros. Instead, the idea is to run gmid and let it dump the configuration once it's been parsed in a static and predictable format. Now is possible to parse gmid configuration with, say, awk or perl.
Diffstat (limited to 'gmid.1')
-rw-r--r--gmid.12
1 files changed, 2 insertions, 0 deletions
diff --git a/gmid.1 b/gmid.1
index b9944ea..3912103 100644
--- a/gmid.1
+++ b/gmid.1
@@ -62,6 +62,8 @@ in the config file if present.
Stays and logs on the foreground.
.It Fl n
Check that the configuration is valid, but don't start the server.
+If specified two or more time, dump the configuration in addition to
+verify it.
.It Fl P Pa pidfile
Write daemon's pid to the given location.
.Ar pidfile