[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zfs-discuss
Subject:    Re: [zfs-discuss] file expiration date/time
From:       Dennis Yurichev <dennis () conus ! info>
Date:       2009-12-30 21:39:14
Message-ID: 4B3BC882.2050208 () conus ! info
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Elling wrote:
>>> Why each file can't have also "expiration date/time" field, e.g.,
>>> date/time when operation system will delete it automatically?
>>> This could be usable for backups, camera raw files, internet browser
>>> cached files, etc.
>>
>> Using extended attributes + cron, you could provide the same service
>> yourself and other similar (or not) things people would like to do
>> without developers providing it for you in the fs..
> 
> I recall a long discussion about this sort of feature on usenet back in
> the late '80s. The problem is that deletion is not a good result.  For
> example, suppose you run a server for a year with a year expiry
> policy. Will it be able to reboot?  Some files are only accessed at
> boot time, so how will you know what files are good candidates?

This attribute could be optional and to be set by user or software
program running by user.


- --
My PGP public key: http://yurichev.com/dennis.yurichev.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAks7yIIACgkQ1YPmFmJG++NTdgCg0HtgWI6PRj+NSgLdy/d5in/X
2I8An0/lfdSlp/Ed6l8xhU5x/IJvxDiQ
=HIe1
-----END PGP SIGNATURE-----
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
[prev in list] [next in list] [prev in thread] [next in thread]