Disregard my last. $ timeout 1 bash -c "echo foo > pipe"
...does work. I'm not sure why I thought it didn't. Sent with Proton Mail secure email. On Tuesday, December 16th, 2025 at 8:31 AM, Code Con Carne <[email protected]> wrote: > > > Thanks for your response. I thought I understood until I tried > > $ timeout 1 bash -c "echo foo > pipe" > > > but that doesn't work either. I achieved my intent with dd and a > here-document. > > Sent from Proton Mail for Android. > > -------- Original Message -------- > On Monday, 12/15/25 at 06:28 Pádraig Brady [email protected] wrote: > > On 15/12/2025 03:08, Collin Funk wrote: > > > I agree that this behavior isn't obvious. :) > > > We should probably better document timeout's interactions with shell > constructs, > as it's a common question and tricky to see what's going on: > > https://unix.stackexchange.com/questions/727895/capture-process-signal-terminated-message-output-in-shell-pipeline > https://superuser.com/questions/1260918/bash-pipeline-signal-propagation-how-does-it-work/1261201#1261201 > https://stackoverflow.com/questions/68479811/why-does-usr-bin-timeout-kill-the-entire-pipe/68482748#68482748 > https://unix.stackexchange.com/questions/231526/timeout-breaking-pipes-and-wc/751212#751212 > > I'll see can I come up with something for the info docs > > cheers, > Padraig
