[Nfd-dev] Config file for the library

[Lan Wang (lanwang)]

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/c07b3a2fabc25bc6ad9d3bf9ffc9df7bf994dd96 commit 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20140324/25991cb9/attachment.html>