[Nfd-dev] [EXT] Issue with getting nfd-log

[Eric Newberry]

I don't believe one can make a blanket statement like this. If NFD is 
built from source, start-nfd will directly run NFD with "sudo nfd". 
Additionally, NFD runs perfectly fine on platforms that do not have systemd.

Eric

On 4/16/2020 11:59 AM, Junxiao Shi wrote:
> Hi Eric
>
> The main problems of invoking nfd binary directly are:
> * NFD will fail to start if there’s no key in the keychain.
> * NFD could make certain files in the keychain to become owned by 
> root, and subsequently cause applications under the non-root user 
> account to experience file access errors.
> * Accessing the same keychain from multiple processes could easily 
> trigger underlined behavior. In fact, if NFD binary and ndn-cxx were 
> built with asserts enabled, you run NFD on user keychain and then run 
> ndncert or ndnsec to add a new key, NFD would crash after a few seconds.
>
> Therefore, you should only start NFD with the method specify in 
> packaging: systemd. This ensures NFD is started in the correct uid and 
> a separate keychain.
>
> Yours, Junxiao
>
> On Thu, Apr 16, 2020 at 14:31 Eric Newberry <enewberry at cs.ucla.edu 
> <mailto:enewberry at cs.ucla.edu>> wrote:
>
>     *External Email*
>
>     Hi Ishita,
>
>     In commands 1 and 2 below, I notice that you're specifying "start
>     nfd". If you're trying to run NFD directly, you should rewrite
>     this part of these commands as just "nfd". (To clarify, there is
>     nothing wrong with running NFD directly.)
>
>     Hope this helps!
>
>
>     Eric
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20200416/a4f9713f/attachment.html>