> Nope, actually "-l" does exactly what I want. But a user does not really want
> to specify a log file all the time. Maybe log in ~/.local/share/gnunet by
> default?
Logging to a file by default could be quite cringe-bearing since some
services are prone to busy-loops and this would lead to
> On 30. Apr 2019, at 20:26, Schanzenbach, Martin
> wrote:
>
> Signed PGP part
>
>
>> On 30. Apr 2019, at 20:00, Christian Grothoff wrote:
>>
>> Signed PGP part
>> On 4/30/19 2:08 PM, Schanzenbach, Martin wrote:
>>> Hi,
>>>
>>> everytime I show somebody how to start gnunet, the behaviour
Christian Grothoff transcribed 4.4K bytes:
> On 4/30/19 7:33 AM, IC Rainbow wrote:
> > Maybe it would be useful for quickstarting F2F networks then?
>
> Well, I'd expect F2F networks to generally prefer other mechanisms:
> a hostlist server, or LAN discovery might do just as well. Also, for
>
On 4/30/19 2:08 PM, Schanzenbach, Martin wrote:
> Hi,
>
> everytime I show somebody how to start gnunet, the behaviour of gnunet-arm
> seems to be a major pain point because it exhibits two behaviours which,
> combined, are quite odd.
> Those two are:
>
> 1. gnunet-arm -s does not hang but
On 4/30/19 7:33 AM, IC Rainbow wrote:
> Maybe it would be useful for quickstarting F2F networks then?
Well, I'd expect F2F networks to generally prefer other mechanisms:
a hostlist server, or LAN discovery might do just as well. Also, for
simple exchange of the information without the extra
Christian Grothoff transcribed 4.1K bytes:
> On 4/29/19 9:48 PM, IC Rainbow wrote:
> > Ah, I see. So, I copy that to `share/gnunet/hellos/` and... that would
> > give me what?
>
> Exactly what you wanted: a public key of a peer, an IP address and a
> port to connect to for bootstrapping.
>
> >
Schanzenbach, Martin transcribed 2.4K bytes:
> Hi,
>
> everytime I show somebody how to start gnunet, the behaviour of gnunet-arm
> seems to be a major pain point because it exhibits two behaviours which,
> combined, are quite odd.
> Those two are:
>
> 1. gnunet-arm -s does not hang but return
Hi,
everytime I show somebody how to start gnunet, the behaviour of gnunet-arm
seems to be a major pain point because it exhibits two behaviours which,
combined, are quite odd.
Those two are:
1. gnunet-arm -s does not hang but return the user to the terminal
2. Logging by default is in that
