Conversation
|
So I don't think the config file is actually being parsed. Instead what I've done is pass the config options as command line params through the use of |
|
Since |
| AmbientCapabilities=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE | ||
| CapabilityBoundingSet=CAP_SETPCAP CAP_NET_RAW CAP_NET_BIND_SERVICE | ||
| EnvironmentFile=/etc/hnsd.conf | ||
| ExecStart=/usr/bin/hnsd $HNSD_CONFIG |
There was a problem hiding this comment.
Were you planning on removing $HNSD_CONFIG?
There was a problem hiding this comment.
No, its injected from /etc/hnsd.conf. It's a bit of hack to resemble a configuration file, but all it does is set the env var that gets passed to the executable.
This is only necessary since we don't have config parsing as of yet.
There was a problem hiding this comment.
I'd just recommend that flags be used and a sane default be put in the service file.
eg:
hnsd -r 127.0.0.1:53
WIP: looking for feedback to improve defaults, conflicts with other resolvers, tests on various linux distros etc.