details: https://hg.nginx.org/njs/rev/40f26bb516a6
branches:
changeset: 1020:40f26bb516a6
user: Valentin Bartenev
date: Thu Jun 27 18:55:34 2019 +0300
description:
Removed unused nxt_lvlhsh_ctx_t structure.
diffstat:
nxt/nxt_lvlhsh.h | 10 --
1 files changed, 0 insertions
details: https://hg.nginx.org/njs/rev/9db5e400480c
branches:
changeset: 1019:9db5e400480c
user: Valentin Bartenev
date: Thu Jun 27 18:55:34 2019 +0300
description:
Removed unused nalloc parameter from lvlhsh allocation functions.
diffstat:
njs/njs_event.c | 1 -
njs/n
details: https://hg.nginx.org/njs/rev/0119e834a202
branches:
changeset: 1018:0119e834a202
user: Valentin Bartenev
date: Thu Jun 27 18:54:21 2019 +0300
description:
Version bump.
diffstat:
njs/njs.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diffs (12 lines):
diff
Hi there!
In my day job I'm helping to get applications from traditional
environments running in cloud environments. Cloud native applications
are just "normal" applications, but there are a few properties that
they should satisfy (apart from resiliency and scalability).
For logging this boils do
On Thursday 27 June 2019 19:12:51 Peter Bittner wrote:
> Hi there!
>
> In my day job I'm helping to get applications from traditional
> environments running in cloud environments. Cloud native applications
> are just "normal" applications, but there are a few properties that
> they should satisfy
I may be a bit ignorant about system-level operations, I apologize.
Can you explain why this works better with writing to a file (i.e. the
hardcoded location /var/log/nginx/*.log)?
Peter
On Thu 27 June 2019 19:35 Valentin V. Bartenev wrote:
>
> On Thursday 27 June 2019 19:12:51 Peter Bittner wro
On Thursday 27 June 2019 19:44:22 Peter Bittner wrote:
> I may be a bit ignorant about system-level operations, I apologize.
>
> Can you explain why this works better with writing to a file (i.e. the
> hardcoded location /var/log/nginx/*.log)?
>
[..]
In most cases writing to a file never blocks.
Hmm...
>From _The Linux Programming Interface: A Linux and UNIX System
Programming Handbook_ [2]:
Nonblocking mode can be used with devices (e.g., terminals and
pseudoterminals), pipes, FIFOs, and sockets. (Because file descriptors
for pipes and sockets are not obtained using open(), we must
