Timeline for make tail -f exit on a broken pipe
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2018 at 17:11 | history | edited | Stéphane Chazelas | CC BY-SA 3.0 | added 2 characters in body |
| Jan 10, 2018 at 17:31 | answer | added | Stéphane Chazelas | timeline score: 10 | |
| Jan 10, 2018 at 17:31 | history | reopened | Stéphane Chazelas sed Users with the sed badge or a synonym can single-handedly close sed questions as duplicates and reopen them as needed. | ||
| Jan 10, 2018 at 17:20 | comment | added | Alex028502 | funny thing is what I am trying to do is an accepted answer here: unix.stackexchange.com/a/45943/158192 | |
| Jan 10, 2018 at 17:16 | comment | added | Stéphane Chazelas | The answers there explain why tail -f is not killed when sed exits, when the pipe is broken (because it doesn't write anything after) and how to work around it. | |
| Jan 10, 2018 at 17:15 | comment | added | Alex028502 | I don't think either of those are similar to this question. One is about writing your own program (in golang) that exits when the pipe is broken. This question is specifically about tail -f and asking why something in a previous answer doesn't work. | |
| Jan 10, 2018 at 16:52 | history | closed | Stéphane Chazelas sed Users with the sed badge or a synonym can single-handedly close sed questions as duplicates and reopen them as needed. | Duplicate of How to exit early on pipe close? | |
| Jan 10, 2018 at 16:51 | comment | added | Stéphane Chazelas | Similar: unix.stackexchange.com/a/366806/22565 | |
| Jan 10, 2018 at 16:40 | history | asked | Alex028502 | CC BY-SA 3.0 |