Opened 12 years ago
Closed 12 years ago
#145 closed task (fixed)
flarmclient only finds config files, if installed in home directory
| Reported by: | dominic | Owned by: | dominic |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Ground-Station | Version: | 1.2.0 (Usability) |
| Keywords: | Cc: |
Description
flarmclient only finds its associated config files correctly, if installed in /home/pi/. Installing it in /home/pi/flarmradar will corrupt the default path search routine.
Proposal: Search for config files relative to location of flarmclient.pl. This will enable users to place the flarmclient in any directory structure.
Change History (4)
comment:1 Changed 12 years ago by
| Status: | new → assigned |
|---|
comment:2 Changed 12 years ago by
| Status: | assigned → accepted |
|---|
comment:3 Changed 12 years ago by
comment:4 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
That is now configurable (option -c).
The algorithm for finding the config file is as follows:
- check for option -c, use the indicated file if this option is given
- check in /etc/flarmclient.conf, use this file if present
- check if a file named flarmclient.conf exists in the local directory
- otherwise: bail out
Note: See
TracTickets for help on using
tickets.
![(please configure the [header_logo] section in trac.ini)](/trac/flarmradar/chrome/site/your_project_logo.png)
Targeted installation method is via a software package. Then the Unix-style approach is the correct one.
Having multiple clients running is probably something that the developers want to do, ... and then the option -c to use multiple config files in different locations should be sufficient.