Hi,
Hiltjo Posthuma wrote on Fri, Dec 20, 2019 at 12:40:14AM +0100:
> On Thu, Dec 19, 2019 at 02:03:19PM -0700, andrej wrote:
>> On the note of accurate documentation; how about adding the actually
>> defined timeout for persist rather than the "some time"?
> Sometimes there is a reason implemen
On Thu, Dec 19, 2019 at 02:03:19PM -0700, andrej wrote:
> Hi Ted,
>
> On the note of accurate documentation; how about adding the actually defined
> timeout for persist rather than the "some time"?
>
>
> Cheers,
> Andrej
>
>
>
> --
> Sent from: http://openbsd-archive.7691.n7.nabble.com/openbs
Hi Ted,
On the note of accurate documentation; how about adding the actually defined
timeout for persist rather than the "some time"?
Cheers,
Andrej
--
Sent from: http://openbsd-archive.7691.n7.nabble.com/openbsd-user-misc-f3.html
Understood (though in this case it looks unfinished when 99% of the
implementation is already present).
In any case you have answered my original question. Thanks, Ted.
On Tue, 14 Mar 2017 18:29:25 -0400
"Ted Unangst" wrote:
> bytevolc...@safe-mail.net wrote:
> > I'm not saying "you must do eve
bytevolc...@safe-mail.net wrote:
> I'm not saying "you must do everything my way or else", but rather I
> am trying to understand the reasoning behind making this hardcoded and
> fixed, as opposed to being admin-settable; maybe something is planned
> here I am unaware of?
We're trying to keep the
>From what I have read, it appears to be 15 minutes on some systems and
30 minutes on others, and this can be adjusted by the admin without
having to recompile the code.
I'm not saying "you must do everything my way or else", but rather I
am trying to understand the reasoning behind making this ha
bytevolc...@safe-mail.net wrote:
> On one box I test configuration edits and backups, I find myself using
> doas around once every 7-9 minutes, exceeding the 5 minute limit.
> Another box is basically a gateway, so I don't exceed 2 minutes between
> doas runs.
The timeout was originally 10 minutes
On one box I test configuration edits and backups, I find myself using
doas around once every 7-9 minutes, exceeding the 5 minute limit.
Another box is basically a gateway, so I don't exceed 2 minutes between
doas runs.
It would be nice to have the option of deviating from the default, and
the "pe
I'll ask the question: Why are you sure you need that?
> Are there plans (or perhaps code already being worked on) to allow
> doas(1) 'persist' to have a different time other than 5 minutes? I am
> thinking of writing a patch for this, but I do not want to duplicate
> effort if the devs have other
Hi,
Are there plans (or perhaps code already being worked on) to allow
doas(1) 'persist' to have a different time other than 5 minutes? I am
thinking of writing a patch for this, but I do not want to duplicate
effort if the devs have other/similar plans ahead.
I would like to configure the timeou
10 matches
Mail list logo