Re: deleting content of /tmp
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/25/07 05:01, CaT wrote:
> On Sat, Mar 24, 2007 at 11:25:08PM -0500, Ron Johnson wrote:
>> tmpfile()
>> Return a new file object opened in update mode ("w+b").
>> The file has no directory entries associated with it and
>> will be automatically deleted once there are no file
>> descriptors for the file. Availability: Macintosh, Unix,
>> Windows.
>>
>> What I meant was os.tempnam(). Which the documentation indicates is
>> vulnerable to symlink attacks.
>>
>> Not being able to exclusively lock a file is a definite weakness.
>
> Christ, no. It makes backups a buttload more complicated then they
> otherwise need be. I absolutely loathe backing up windows files beacuse
> of what mostlikely is a similar attitude. That's bad design.
tar just doesn't have enough OS knowledge.
OpenVMS BACKUP (as always, dependent on the process's privileges)
only backs up closed files. BACKUP/INTERLOCK (still dependent on
the process's privileges) has a special only-for-BACKUP feature that
allows it access to open files. Dave Cutler must have forgotten
that feature when designing Windows NT.
BCKUP's /EXCLUDE syntax is also much nicer than "tar --exclude", but
that's a different story.
> All in all I think you're making a mountain out of flat grass-plains
> here. There is nothing inherently faulty, false or wrong in what the
> zebra do there. For one, it makes sure that it is truly temporary. If
> the app exits in some bizare way then no harm done.
There are simple ways around that.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGBpu6S9HxQb37XmcRAg2mAJ9LFksfbP6KP8iHI24CaxDulHOgLgCg3rYD
3T/f5d6YbC+qMyxzJO3Xb8c=
=Kub/
-----END PGP SIGNATURE-----
Reply to: