On Wed, Oct 04, 2023 at 09:22:00AM +0200, Kirill Miazine wrote: > user, group and chroot arguments for the filter option were not documented
If we're going to document the chroot option, it _might_ be worth adding a note that the chroot environment needs /bin/sh to be present in order for the filter to actually be launched. This doesn't really affect users who are using exisiting third-party filters, but if you're writing your own one the error message when /bin/sh is missing is something along the lines of: warn: lost processor: foo exited abnormally ... which doesn't give any clue as to what the real problem is.
