Message78444
| Author | pitrou |
|---|---|
| Recipients | mrts, pitrou |
| Date | 2008-12-29.10:05:04 |
| SpamBayes Score | 0.0051686205 |
| Marked as misclassified | No |
| Message-id | <1230545107.10188.1.camel@localhost> |
| In-reply-to | <1230540365.94.0.963262339481.issue4489@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> A blunt, ineffective solution would be to walk the tree before removing > it and recording path : inode pairs in a dict on first pass and then > checking that the inodes have not changed during removal on second pass. There's no way to do the "check inode then remove" sequence atomically. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-12-29 10:05:05 | pitrou | set | recipients: + pitrou, mrts |
| 2008-12-29 10:05:04 | pitrou | link | issue4489 messages |
| 2008-12-29 10:05:04 | pitrou | create | |