[2024-11-15T00:01:33Z] <riteo> sewn: sorry for the delay
[2024-11-15T00:02:11Z] <riteo> I have a script that writes things into a fifo and it just keeps going once the reading end closes 
[2024-11-15T00:02:22Z] <riteo> Perhaps there's a saner mechanism I'm ignoring?
[2024-11-15T00:03:02Z] <riteo> midfavila: sorry, did I sin that much with that phrase
[2024-11-15T00:03:15Z] <riteo> no idea what I'm getting into lol
[2024-11-15T00:03:27Z] * riteo holds onto garlic bread tighter
[2024-11-15T00:33:05Z] <sad_plan> riteo: put it into a loop then?
[2024-11-15T00:46:53Z] <sad_plan> or run it with -x or -v or both, to figure out where/why it fails
[2024-11-15T01:23:10Z] <riteo> sad_plan: I did both of those
[2024-11-15T01:23:14Z] <riteo> like a subshell and everything
[2024-11-15T01:23:26Z] <riteo> if I replace date with `printf "%s\n" "$(date)"` it works
[2024-11-15T01:23:53Z] <riteo> it's inside a `while sleep 1` loop
[2024-11-15T01:27:31Z] <sad_plan> wierd
[2024-11-15T01:32:27Z] <riteo> I have a feeling that it might be a busybox default thing
[2024-11-15T01:32:48Z] <riteo> like, looking the issue around it seems that they had to patch sigpipe handling directly into ip or some other utility
[2024-11-15T01:33:06Z] <riteo> this is backed by like 0 things so ye I definitely know what I'm talking about
[2024-11-15T01:33:22Z] <riteo> oh I think I just understood what mid was saying
[2024-11-15T01:33:36Z] <riteo> it was not for sigpipe lol
[2024-11-15T01:57:23Z] <sad_plan> lol
[2024-11-15T18:48:57Z] <sewn> testuser[m]: