IN the long run, yes, we may want to make the signal different or
configurable. Our current plan is to try this internally first and see how
the ops guys like it, or if they have problems making it work. At this
point, going with SIGUSR2 is IMHO the best option, because the cost of
fixing it later
Thanks. Good point about the custom signal: logrotate and newsyslog seem to
be the most popular log rotation utilities and they both support a custom
signal.
On Thu, Jan 23, 2020 at 12:09 PM Derek Dagit wrote:
> +1 for concept and rationale
>
> Might be good to survey the common log rotation too
+1 for concept and rationale
Might be good to survey the common log rotation tools to verify custom
signals are supported.
On Thu, Jan 23, 2020 at 11:16:25AM -0600, Brian Neradt wrote:
>
> Context
> ==
>
> Traffic Server currently implements its own mechanism for rotating its logs
> and cle
Context
==
Traffic Server currently implements its own mechanism for rotating its logs
and cleaning up (i.e., deleting) rotated logs based upon configured
constraints. These features seem to have been developed at a time when
third party tools for managing such logs were non-existent or immatu