Timeline for Closing a file descriptor, >&- vs <&-
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 27, 2017 at 8:04 | comment | added | CMCDragonkai | I don't think that's what I meant. Just that a a read write file descriptor can be closed using 3>&- and 3<&- as well. | |
| Feb 27, 2017 at 3:39 | comment | added | Rockallite | @CMCDragonkai Run exec 3<>&-, and you'll get an error: -bash: syntax error near unexpected token `&'. Bash 4.2 here. | |
| Feb 17, 2016 at 11:05 | comment | added | cuonglm | I can't get what you mean. Please give an example./ | |
| Feb 17, 2016 at 11:01 | comment | added | CMCDragonkai | That closing <> can be done via the same ways. | |
| Feb 17, 2016 at 9:44 | comment | added | cuonglm | @CMCDragonkai: I know! But what do you mean This can be used on <> file descriptors too? | |
| Feb 17, 2016 at 9:35 | comment | added | CMCDragonkai | <> is a read/write file descriptor, allowing one to read and write to the descriptor. | |
| Feb 17, 2016 at 9:01 | comment | added | CMCDragonkai | No that's not possible, but as in 3>&- or 3<&- appears to close the descriptor. | |
| Feb 17, 2016 at 4:42 | comment | added | CMCDragonkai | This can be used on <> file descriptors too. | |
| May 24, 2014 at 20:11 | vote | accept | Jason | ||
| May 24, 2014 at 18:23 | history | answered | cuonglm | CC BY-SA 3.0 |