Recall that 2.2 ran piped loggers under a shell until somewhat late in life, and 2.4 runs them directly [by default].
rotatelogs currently doesn't do anything to block sigterm. The default ahndler for sigterm writes a short message to stderr, which is the only reason I noticed. It seems like a lose/lose scenario though: If rotatelogs exits early due to sigterm before all writing ends of the pipe are closed, it's not there to log the stragglers for e.g. a graceful restart If rotatelogs waits... then replacement rotatelogs processes are likely to write to the same log [if using time based rotation]. Any other ideas/observations/trivia? -- Eric Covener cove...@gmail.com
