Leon Sodhi

I'm seeing the same behaviour here on a Linux box. We could add something into each init script, but that means it would still be broken for anyone that wants...

Thanks, @manuelmeurer, and that Docker implementation is particularly interesting. Looks like they're handling signals [here](https://github.com/docker/docker/blob/08c5f52d70e539ff168d570b60b0c5d6c1a847c2/docker/daemon.go#L288), which relies on their [signal](https://github.com/docker/docker/blob/84be89a273742b24bb9a87ea5ccfecac97d33bfc/pkg/signal/trap.go#L22) lib and the removal function you linked to. The [mirrorbits](https://github.com/etix/mirrorbits/blob/3dcb042bbf5c7ce3f247f17294df5be77a876bc8/main.go#L83)...

There was some work done to solve this in the linked "Issue 11" PR. I think [this](https://github.com/papertrail/remote_syslog2/blob/dfb6b3e028ed6dde07f11de9c907a20619abf672/glob.go#L39) would do it. That said, we can't risk merging it as so much...

Thanks, @tuupola. Let me play with this to see what effect it has. Assuming all is well, I'll apply one of the suggested fixes and merge.

Not sure. Only had one confirmed case of it although I have heard of people accidentally logging email attachments in the past. I'd be inclined to consider this low priority...

I have no experience with this kind of thing, but I'd guess it is and that we do want to sign our packages so that folks know they came from...

Partially solves: http://jira.qos.ch/browse/LOGBACK-1011