Timeline for How to read the whole shell script before executing it?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 21, 2021 at 0:11 | comment | added | Charles Duffy | @musiphil, whether you unlink the file or rename a new inode to have the old name, the effect is the same -- the old inode remains valid until no references to it exist. What part of my above comment do you believe contradicts that? The race condition is around the directory entry, not the inode. | |
| Sep 20, 2021 at 23:39 | comment | added | musiphil | @CharlesDuffy: If an open file is deleted (asynchronously), doesn't it survive until it's closed (as stated in unlink(2))? | |
| Dec 22, 2016 at 17:37 | comment | added | Charles Duffy | "delete" isn't actually part of the process. If you want to make it properly atomic, you do a rename over the destination file -- if you have a delete step, there's a risk of having your process die after the delete but before the rename, leaving no file in place at all (or a reader try to access the file in that window, and find neither old nor new versions available). | |
| Dec 21, 2016 at 9:27 | history | edited | meuh | CC BY-SA 3.0 | rcs |
| Dec 21, 2016 at 8:52 | history | answered | meuh | CC BY-SA 3.0 |