loial <jldunn2...@gmail.com> writes:
> I have a requirement to test the creation time of a file with the
> current time and raise a message if the file is more than 15 minutes
> old.
> Platform is Unix.
> I have looked at using os.path.getctime for the file creation time and
> time.time() for the current time, but is this the best approach?
No. getctime() returns the last "change" time. The creation time is not
kept anywhere. This may still match your requirement though. And os.path
is the right package to look at for such tasks.
>> I have a requirement to test the creation time of a file with the
>> current time and raise a message if the file is more than 15 minutes
>> old.
>> Platform is Unix.
>> I have looked at using os.path.getctime for the file creation time and
>> time.time() for the current time, but is this the best approach?
> No. getctime() returns the last "change" time. The creation time is not
> kept anywhere. This may still match your requirement though. And os.path
> is the right package to look at for such tasks.
Sorry, it may happen that the filesystem you're working with provides
that time, in which case it's called birthtime. This _may_ be available
via os.stat().
On Wed, 06 Jun 2012 05:50:02 -0700, loial wrote:
> I have a requirement to test the creation time of a file with the current
> time and raise a message if the file is more than 15 minutes old.
> Platform is Unix.
> I have looked at using os.path.getctime for the file creation time and
> time.time() for the current time, but is this the best approach?
Most Unix filesystems don't store a "creation" time.
On Jun 6, 7:50 am, loial <jldunn2...@gmail.com> wrote:
> I have a requirement to test the creation time of a file with the
> current time and raise a message if the file is more than 15 minutes
> old.
> Platform is Unix.
> I have looked at using os.path.getctime for the file creation time and
> time.time() for the current time, but is this the best approach?
Unless you are using ext4 you are going to have to store the creation
time yourself. If the files are coming from your application, use the
sqlite3 or shelve module to store the creation time for each file then
check that data to determine which files are more than 15 minutes old.
If the files are being generated from another application or from
users, have your application check the directory every minute and
record any new files. Worst case scenario, a file will be present for
16 minutes vs 15.
t_texas <tyev...@gmail.com> wrote:
> On Jun 6, 7:50 am, loial <jldunn2...@gmail.com> wrote:
>> I have a requirement to test the creation time of a file with the
>> current time and raise a message if the file is more than 15 minutes
>> old.
>> Platform is Unix.
>> I have looked at using os.path.getctime for the file creation time and
>> time.time() for the current time, but is this the best approach?
> Unless you are using ext4 you are going to have to store the creation
> time yourself. If the files are coming from your application, use the
> sqlite3 or shelve module to store the creation time for each file then
> check that data to determine which files are more than 15 minutes old.
pyinotify might be worth a look
-- -----------------------------------------------------------
| Radovan Garabík http://kassiopeia.juls.savba.sk/~garabik/ |
| __..--^^^--..__ garabik @ kassiopeia.juls.savba.sk |
-----------------------------------------------------------
Antivirus alert: file .signature infected by signature virus.
Hi! I'm a signature virus! Copy me into your signature file to help me spread!
