On 08/02/2015 22:12, Olivier Brunel wrote:
Except for that bit. I don't like that, and I'd really like an option to
turn that behavior off. Specifically, in my case the only scenario I can
imagine where the write would fail, i.e. daemon is down, would be
because it crashed/was restarted; Neither
TIMESTAMP is 25 char long, so just enough for the tainstamp with its @-prefix.
This was actually overwriting the last character in the tainstamp!
Applied, thanks.
The *_FMT macros are one more than the max length for the type, to account for
a possible final \0. The TIMESTAMP macro is not.
T
On 02/07/15 17:17, Laurent Bercot wrote:
> On 27/01/2015 01:10, Laurent Bercot wrote:
>> Something like that. I haven't given it any thought yet
>
> So I've experimented a lot with that. I've put in knobs
> and turned and tweaked them, I've put guards on the number of
> forks per second, and gu
Signed-off-by: Olivier Brunel
---
TIMESTAMP is 25 char long, so just enough for the tainstamp with its @-prefix.
This was actually overwriting the last character in the tainstamp!
src/daemontools-extras/s6-log.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/daemon
