[Nfd-dev] config file installing
Alex Afanasyev
alexander.afanasyev at ucla.edu
Wed Mar 12 11:46:52 PDT 2014
Ok. Then it simplifies the job and everything is getting more straightforward.
Another question. What about creating default.key file that is authorized for everything. Is it also should be deferred to the package manager?
---
Alex
On Mar 12, 2014, at 11:42 AM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
> "./waf install" or "make install" is a command to *install* a software. It just needs to install a **sample** configuration file to /etc/ndn/nfd.conf.sample .
> `nfd` program requires a command line argument for the path to configuration file. User must copy the sample cconfiguration file, and pass its path as the argument.
>
> Package has a post-install step, which should:
>
> 1. copy the sample to /etc/ndn/nfd.conf , if it doesn’t exist
> 2. perform a dry-run, to guard against an incompatible configuration
> 3. setup upstart job that has the configuration file path
>
> Yours, Junxiao
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140312/cc501a51/attachment.html>
More information about the Nfd-dev
mailing list