On 5/2/19 3:34 PM, n...@n0.is wrote:
>
> Spoiler: no. And we can't know which OS rotates, and which ones don't.
> I think what we can agree on is that what we have right now is
> suboptimal. But I agree, logging to the $HOME location is not ideal
> either, but a step forward.
Oh, we technically
Christian Grothoff transcribed 4.5K bytes:
> On 5/2/19 10:44 AM, Hartmut Goebel wrote:
> > Am 01.05.19 um 10:35 schrieb Christian Grothoff:
> >> Are you aware that our logging subsystem can do log rotation (and that
> >> we would then only keep the logs for the last 3 days)?
> >
> >
> > IMO
On 5/2/19 10:44 AM, Hartmut Goebel wrote:
> Am 01.05.19 um 10:35 schrieb Christian Grothoff:
>> Are you aware that our logging subsystem can do log rotation (and that
>> we would then only keep the logs for the last 3 days)?
>
>
> IMO gnunet should not re-implement operating system tasks, for
Am 01.05.19 um 10:35 schrieb Christian Grothoff:
> Are you aware that our logging subsystem can do log rotation (and that
> we would then only keep the logs for the last 3 days)?
IMO gnunet should not re-implement operating system tasks, for several
reasons:
- logging should be done using the
I've now changed arm.conf.in to log by default to a file when one starts
gnunet-service-arm via gnunet-arm (note that if you launch
gnunet-service-arm by hand or via systemd, the default remains stderr).
Logging is done to ~/.cache/gnunet/gnunet--MM-DD.log, log rotation
should prevent the
On Wed, May 1, 2019 at 11:36 AM Christian Grothoff wrote:
>
> On 5/1/19 7:45 AM, IC Rainbow wrote:
> >> 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
On 5/1/19 7:45 AM, IC Rainbow wrote:
>> 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
> 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
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
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
12 matches
Mail list logo
