Message78442
| Author | mrts |
|---|---|
| Recipients | mrts, pitrou |
| Date | 2008-12-29.08:41:49 |
| SpamBayes Score | 0.00032891618 |
| Marked as misclassified | No |
| Message-id | <1230540111.7.0.0240777467539.issue4489@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Aha, got it -- while removing /a/b/c/d, there's no easy way to detect
that b or c has become a symlink.
I.e.
given directory tree
a
`-- b
|-- c
`-- d
1. os.rmdir('/a/b/c') succeeds
2. execution is suspended
3. '/a/b' is made a symlink to a path that contains 'd'
4. '/a/b/d' is neither a symlink, nor has it's inode been recorded, so
os.rmdir('/a/b/d') succeeds
I'm afraid the solution for the Perl bug is susceptible to the same problem. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-12-29 08:41:51 | mrts | set | recipients: + mrts, pitrou |
| 2008-12-29 08:41:51 | mrts | set | messageid: <1230540111.7.0.0240777467539.issue4489@psf.upfronthosting.co.za> |
| 2008-12-29 08:41:50 | mrts | link | issue4489 messages |
| 2008-12-29 08:41:49 | mrts | create | |