Broken pipe when using | tee

[jwilm]

I've been running a process into a | tee logfile; sending SIGINT will close everything down, but log4rs prints a bunch of this to stdout at that point:

log4rs: Broken pipe (os error 32)
log4rs: Broken pipe (os error 32)
log4rs: Broken pipe (os error 32)
log4rs: Broken pipe (os error 32)
log4rs: Broken pipe (os error 32)

This is on macOS and a few months old version of log4rs; haven't tested a newer version or different OS.

[sfackler]

I don't think log4rs is doing anything particularly interesting here. I'm guessing that SIGINTing the process group will sometimes kill the tee first so stdout breaks. The error logging goes to stderr which presumably wasn't redirected. I've been meaning to make the error logging configurable but haven't gotten around to it.

[sfackler]

Are there any actions to take here?

[jwilm]

Hey sorry for not getting back to you. I guess if this is how things usually work, then there's no action needed. My application actually does a graceful shutdown on SIGINT so it's probably trying to log after the pipe is closed.

[sfackler]

No problem! I filed #32 to track the meta-logger stuff.