[Nfd-dev] Help needed with debugging duplicate Nonce

[Ashlesh Gawande (agawande)]

I am not sure but your points make sense. I was just logging the insertion and deletion of PIT entries and in records and out records in the strategy.


It maybe better to put majority of the PIT logging in TRACE as PIT can generate a lot of logs.


Ashlesh

________________________________
From: Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Monday, August 22, 2016 11:18:05 AM
To: Ashlesh Gawande (agawande)
Cc: Lan Wang (lanwang); nfd-dev at lists.cs.ucla.edu
Subject: Re: [Nfd-dev] Help needed with debugging duplicate Nonce

Ashlesh, I'm still waiting for you to answer about what PIT logging you are looking for.
For others on nfd-dev, if you have a need for PIT logging, please let me know the requirements so I can design properly.

I can see a few levels of PIT logging:

  *   track the insertion and deletion of PIT entries: although PIT has no logging, this can be inferred from Forwarder logging at DEBUG level; however, having logging from PIT makes this easier
  *   track the PIT timers: they are currently controlled by Forwarder (not PIT), and can be inferred from Forwarder logging at DEBUG level
  *   track the in/out records: although PIT has no logging, this can be inferred from Forwarder logging at DEBUG level; however, having logging from PIT makes this easier
  *   track changes in StrategyInfo: this is controlled by specific strategy and should be implemented by strategy

Yours, Junxiao

On Wed, Aug 10, 2016 at 8:27 AM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:
Hi Ashlesh

You can't. FIB/PIT/Measurements has no logging. If this is a popular demand, I may consider adding it.
You can let me know what kind of PIT logging you are looking for, so that if I decide to work on this, I can have a better idea on the use cases.

Currently you can use a debugger, or add printfs at where matters.

Yours, Junxiao

On Wed, Aug 10, 2016 at 8:19 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Can you please tell me how to deduce PIT entry contents by looking at the NFD log?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160822/56720ca3/attachment.html>