I noticed that running s6-log as follows still creates few archived logs:
Thanks for the report. Does s6-log send any warnings to its own stderr (which may or may not be caught by your supervision infrastructure) ? Can you please send a strace of a s6-log run where you observe the behaviour ? -- Laurent
