[hipl-dev] [Bug 693834] Re: maintain configuration files as separate files
- From: Stefan Götz <693834@xxxxxxxxxxxxxxxxxx>
- To: hipl-dev@xxxxxxxxxxxxx
- Date: Wed, 05 Jan 2011 11:41:26 -0000
I think the usual approach of most other daemons is
1) search for the config file at the configured and compiled-in location
(usually /etc or /usr/local/etc)
2) search for the config file in a user-specific location (not
applicable with HIPL) or the working directory
It depends on the daemon whether they skip step 2) if step 1) succeeds
or whether they read file 2) in addition to file 1). I guess the
skipping approach makes the most sense for HIPL?
It might make sense to add a etc/hip directory to the source tree. It
might also make sense to move all source code into a common src/ sub-
directory (this is what a lot of projects do) (I know unrelated to this
bug report).
--
You received this bug notification because you are a member of HIPL core
team, which is subscribed to HIPL.
https://bugs.launchpad.net/bugs/693834
Title:
maintain configuration files as separate files
Status in Host Identity Protocol for Linux:
Confirmed
Bug description:
The configuration files of hipd, hipfw and related HIPL programs are
currently maintained in-source at hipd/init.c.
Examples are:
- HIPL_CONFIG_FILE_EX
- HIPL_HOSTS_FILE_EX
- HIPL_NSUPDATE_CONF_FILE_EX
- hip_init_certs()
This is ugly and leads to the side-effect that hipd needs to be run for the
first time before hipfw can be started, as it needs to generate
firewall_config. Furthermore, as the configuration files are not explicitly
shipped in the distribution packages, they will not be removed on purge.
We need to maintain configuration in separate files, add them to configure.ac
and ensure that the configuration files can also be found in case of running
hipd from source without prior make install.
Other related posts:
