summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorJakub Jirutka <jakub@jirutka.cz>2022-06-15 18:53:50 +0200
committerDaniel Wagner <wagi@monom.org>2022-08-28 17:40:55 +0200
commit33389f7edcab6d4acb1f30f51a6d838fe49ac022 (patch)
tree53580624660c7e64ac36f8212357f0f3ea4d5d2a /HACKING
parent363e0ed955f605fb0dc919b7ee149b6071af73ee (diff)
downloadconnman-33389f7edcab6d4acb1f30f51a6d838fe49ac022.tar.gz
resolver: Add path to resolv.conf to config options
Before (current state): If the <STATEDIR> (/var/run/connman) directory exists, ConnMan writes resolvfile into <STATEDIR>/resolv.conf. If it doesn't exist, it writes into /etc/resolv.conf. If it fails, it does nothing. Problem: This is unclear and error prone. The user (or package maintainer) may create the /var/run/connman directory for a pidfile or whatever and surely doesn't expect ConnMan to suddenly stop updating /etc/resolv.conf. Or the user doesn't want ConnMan to touch /etc/resolv.conf (e.g. openresolv or similar tool is used), ever. Configuring this use case by creating directory /run/connman (as suggested e.g. on https://wiki.archlinux.org/title/ConnMan#/etc/resolv.conf) is really weird... and error prone. After: The user can explicitly set path for the resolvfile in connman.conf via "ResolvConf" option. If this option is set, ConnMan writes resolvfile to the specified file (and creates it if doesn't exist). If it fails (e.g. directory doesn't exist or file is not writable) or the path is /dev/null or an empty string, it does nothing. If this option is not set, it behaves as before. Signed-off-by: Daniel Wagner <wagi@monom.org> Link: https://lore.kernel.org/r/20220615165350.11431-1-jakub@jirutka.cz
Diffstat (limited to 'HACKING')
0 files changed, 0 insertions, 0 deletions