Mercurial > hg > nginx-quic
view src/core/ngx_syslog.h @ 7286:d27aa9060c95
Stream: udp streams.
Previously, only one client packet could be processed in a udp stream session
even though multiple response packets were supported. Now multiple packets
coming from the same client address and port are delivered to the same stream
session.
If it's required to maintain a single stream of data, nginx should be
configured in a way that all packets from a client are delivered to the same
worker. On Linux and DragonFly BSD the "reuseport" parameter should be
specified for this. Other systems do not currently provide appropriate
mechanisms. For these systems a single stream of udp packets is only
guaranteed in single-worker configurations.
The proxy_response directive now specifies how many packets are expected in
response to a single client packet.
author | Roman Arutyunyan <arut@nginx.com> |
---|---|
date | Mon, 04 Jun 2018 19:50:00 +0300 |
parents | 7f9935f07fe9 |
children | 29adacffdefa |
line wrap: on
line source
/* * Copyright (C) Nginx, Inc. */ #ifndef _NGX_SYSLOG_H_INCLUDED_ #define _NGX_SYSLOG_H_INCLUDED_ typedef struct { ngx_uint_t facility; ngx_uint_t severity; ngx_str_t tag; ngx_addr_t server; ngx_connection_t conn; unsigned busy:1; unsigned nohostname:1; } ngx_syslog_peer_t; char *ngx_syslog_process_conf(ngx_conf_t *cf, ngx_syslog_peer_t *peer); u_char *ngx_syslog_add_header(ngx_syslog_peer_t *peer, u_char *buf); void ngx_syslog_writer(ngx_log_t *log, ngx_uint_t level, u_char *buf, size_t len); ssize_t ngx_syslog_send(ngx_syslog_peer_t *peer, u_char *buf, size_t len); #endif /* _NGX_SYSLOG_H_INCLUDED_ */