Re: [DISCUSS] stop logging errors when named pipe is full

2018-09-05 Thread Leif Hedstrom
> On Sep 5, 2018, at 9:36 AM, Bryan Call wrote: > > How about warning periodically or having a configuration option to disable > the error message? I think rate limiting warnings is a good idea. +1. Heck, I might even suggest that Warning() ought to have that built in :-). I looked at the

Re: [DISCUSS] stop logging errors when named pipe is full

2018-09-05 Thread Bryan Call
How about warning periodically or having a configuration option to disable the error message? -Bryan > On Sep 5, 2018, at 7:41 AM, Emanuele Rocca wrote: > > Hi, > > on busy servers, using named pipes as a log destination is a useful way > to avoid wasting disk space and bandwidth [1]. Howev

[DISCUSS] stop logging errors when named pipe is full

2018-09-05 Thread Emanuele Rocca
Hi, on busy servers, using named pipes as a log destination is a useful way to avoid wasting disk space and bandwidth [1]. However, Traffic Server currently logs an error message when the buffer fills up because no process is reading from the pipe. On a test system, we've seen lots of "Failed to