>>>>> On Thu, 16 Apr 2009 10:33:43 +0800, Craig Ringer said: > > ---------------------------------------- > [C] Things we can and should get rid of: > ---------------------------------------- > > - [st_dev] ID of device containing file > - [st_atime] Last accessed time > - [st_ctime] Time of last status/inode change > - [st_ino] Inode number > - [st_rdev] Device ID (if special file) > - [st_blksize] System I/O block size > - [st_blocks] Number of 512B (not "system block size"?) blocks
I think the new accurate backup code uses st_ctime. > In the above, mtime is defined as a database `timestamp' rather than > stored as the raw integer value from the source host. Note that the > database may not store timestamps with the same precision as the fd > host, and may store them using an internal floating-point form, so some > error must be allowed for during verification. Inaccuracy in mtime and ctime would break the accurate backups code. __Martin ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
