[Nfd-dev] Config file for the library

[Steve DiBenedetto]

There's a missing "else" in the code and the fix is in code review:
http://gerrit.named-data.net/#/c/559/ . Sorry about that.


On Mon, Mar 24, 2014 at 11:27 AM, Syed Obaid Amin <obaidasyed at gmail.com>wrote:

> Hi Alex,
>
> I am not able to start nrd and getting this error:
> ERROR: Cannot create controller for unsupported protocol "nrd-0.1"
>
> This is what I am doing:
> On Terminal 1:
> ~$ sudo NFD_LOG=all nfd
> DEBUG: [NameTree] lookup /
> DEBUG: [NameTree] insert /
> DEBUG: [NameTree] Name / hash value = 2654435816  location = 488
> <Long list of messages>
>
>
> On Terminal 2:
> ~$ cat ~/.ndn/client.conf
> unix_socket=/var/run/nfd.sock
> protocol=nrd-0.1
>
> ~$ nrd
> $ nrd
> ERROR: Cannot create controller for unsupported protocol "nrd-0.1"
>
>
> Commit details
> NFD:             ba7490517d1f4e9b699d7398788db03e1ffaeacc
> ndn-cpp-dev: c07b3a2fabc25bc6ad9d3bf9ffc9df7bf994dd96
> NRD:            ea56c614fe3065d3eee933c49a916ce48feae399
>
> Any idea, what's going wrong here.
>
> Regards,
> Obaid
>
>
> On Mon, Mar 24, 2014 at 8:40 AM, Steve DiBenedetto <
> dibenede at cs.colostate.edu> wrote:
>
>> "protocol" determines the Controller that should be used by faces (see
>> Face::construct()). ndnd-tlv will use a ndnd::Controller (instead of nrd::
>> or nfd::). ndnx-0.7 will throw a Face::Error exception because it is
>> unsupported for ndn-cpp-dev.
>>
>>
>> On Mon, Mar 24, 2014 at 7:25 AM, Lan Wang (lanwang) <lanwang at memphis.edu>wrote:
>>
>>>  What happens when the protocol is ndnd-tlv-0.7
>>> or ndnx-0.7?
>>>
>>>  Lan
>>>
>>>
>>>
>>> -------- Original message --------
>>> From: Alex Afanasyev <alexander.afanasyev at ucla.edu>
>>> Date: 03/23/2014 12:19 PM (GMT-06:00)
>>> To: "<nfd-dev at lists.cs.ucla.edu>" <nfd-dev at lists.cs.ucla.edu>
>>> Subject: [Nfd-dev] Config file for the library
>>>
>>>
>>>  Hi guys,
>>>
>>> I just merged
>>> https://github.com/named-data/ndn-cpp-dev/commit/c07b3a2fabc25bc6ad9d3bf9ffc9df7bf994dd96commit to ndn-cpp-dev library, which changes how the library selects which
>>> protocol to use to register prefixes and where to look for UNIX socket.
>>>
>>> NFD=1 and NRD=1 environmental variables are no longer used.  All
>>> configuration should be done either using ~/.ndn/client.conf, @SYSCONFDIR@/ndn/client.conf
>>> (e.g., /usr/local/etc/ndn/client.conf), or /etc/ndn/client.conf
>>>
>>> The sample config file is in root folder of ndn-cpp-dev repo.  Just in
>>> case, I'll post it here:
>>>
>>> ; "unix_socket" specifies the location of the NFD unix socket
>>> unix_socket=/var/run/nfd.sock
>>>
>>> ; "protocol" deteremines the protocol for prefix registration
>>> ; it has a value of:
>>> ;   nfd-0.1
>>> ;   nrd-0.1
>>> ;   ndnd-tlv-0.7
>>> ;   ndnx-0.7
>>> protocol=nrd-0.1
>>>
>>> ---
>>> Alex
>>>
>>>
>>> _______________________________________________
>>> Nfd-dev mailing list
>>> Nfd-dev at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>>
>>> _______________________________________________
>>> Nfd-dev mailing list
>>> Nfd-dev at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>>
>>>
>>
>> _______________________________________________
>> Nfd-dev mailing list
>> Nfd-dev at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>
>>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140324/f2735ab9/attachment.html>