Comment 4 for bug 693834
Revision history for this message
| Stefan Götz (stefan.goetz-deactivatedaccount) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
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).