[INSTRM-203] consider to move tftp lines to site specific configuration Created: 22/Sep/17 Updated: 05/Apr/19 |
|
| Status: | Open |
| Project: | Instrument control development |
| Component/s: | ics_dnsmasq |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | shimono | Assignee: | cloomis |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | 2017-10A |
| Reviewers: | cloomis |
| Description |
|
tftp option will be used site specific, also tftp source directory would differ. |
| Comments |
| Comment by shimono [ 24/Oct/17 ] |
|
Source for tftp would differ among sites, e.g. following standardized naming conventions esp at the production. Also cloomis we may have two ways:
I suppose we may want to save files into shared NFS storage, not to lose built environments, and may need to follow naming/mounting conventions - so need to change configuration at least |