[Nfd-dev] Path to nfd.log on linux machine

[Ashlesh Gawande (agawande)]

Start nfd directly instead of using nfd-start and redirect the output to a file:

sudo nfd &> nfd.log &


For adding your own logging to CS (from your other post), I suggest to use section 10.2.2 here:

http://named-data.gitlab.io/TR-NDN-0021-NFD-dev-guide/ndn-0021-nfd-guide.pdf

You can specify ContentStore as the module name in cs.cpp

This way you have greater control over the logging through nfd.conf file similar to Forwarder and can use "ContentStore DEBUG" as you want to.


Ashlesh

________________________________
From: Nfd-dev <nfd-dev-bounces at lists.cs.ucla.edu> on behalf of Aman Maldar <amanmaldar at gmail.com>
Sent: Sunday, September 23, 2018 10:57:51 PM
To: nfd-dev at lists.cs.ucla.edu; mini-ndn at lists.cs.ucla.edu
Subject: [Nfd-dev] Path to nfd.log on linux machine

Hello All,
I am aware that in mini-ndn emulator logs are available for respective nodes at /tmp/minindn/(a/b/c/d)/nfd.log location.

I have enabled the module level logs in /usr/local/etc/ndn/nfd.conf on both machines using,
Forwarder DEBUG
ContentStore DEBUG

This whole setup works fine in mini-ndn.  But now I am running ndnping and ndnpingserver on 2 different physical machines.   Forwarding paths are configured.

ndnping and ndnpingserver are working as expected in terms of processing requests and returning data.

I am not able to find where these generated logs (nfd.log file) are stored on linux machine. I searched the previous threads on nfd-dev, couldn't find an answer.
I would really appreciate if someone can guide me here.

Thanks for you time and help.

--
Regards,
Mr. Maldar Aman M.
University of Massachusetts, Lowell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20180924/e7148031/attachment.html>