search for: mtime

Hello again, as stated earlier there is a problem with mtime setting on directories during healing in replication setup. Today I tested 2.0.5 and found out that the handling is more or less generally buggy for directory mtimes. Simply try this: untar some kernel archive on your local disk and look at the mtime of the created top directory. now untar the same...

...NG[28468]: pbx_spool.c:466 scan_thread: Ooh, something changed / timeout [Kdevcentos5x64*CLI> -- Playing '/tmp/smvoice.28537_0' (escape_digits=0123456789#) (sample_offset 0) ? [Kdevcentos5x64*CLI> [Feb 3 17:14:37] WARNING[28468]: pbx_spool.c:461 scan_thread: atime: 1233699276, mtime: 1233699268, ctime: 1233699268 last: 1233699268 next: 1233699278 now: 1233699277 [Kdevcentos5x64*CLI> [Feb 3 17:14:38] WARNING[28468]: pbx_spool.c:461 scan_thread: atime: 1233699276, mtime: 1233699268, ctime: 1233699268 last: 1233699268 next: 1233699278 now: 1233699278 [Kdevcentos5x64*CLI&gt...

...We use an rsync (rrsync, to be precise) based back-up solution. Every so often an iSCSI based file-system gets brought up and left connected for the night. After a mount event rsync will back that volume up, including server TB of data that haven't been modified, but the ctime is newer than the mtime. Is there a way to stop this behaviour? Cheers, Andrej

On 8 September 2015 at 13:57, Kevin Korb <kmk at sanitarium.net> wrote: Hi Kevin. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The ctime will always be newer or the same as the mtime. This is > because changing the mtime also changes the ctime as does other things > like changing the permissions. > > Rsync only pays attention to the mtime because rsync can set a > specific mtime (--times) but setting a specific ctime is impossible as > it would violate the ba...

Hi all. I prepared a mirror (that is intended to be updated by rsync) by doing the initial copy using cpio (for efficiency on 15 million files). Unfortunately, user, group, and mtime of some directories and files was copied incorrectly. Can I use rsync (GIT) to fix this? Greetings Sven -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.or...

I noticed that rsync is happy to hard-link a device node from a --link-dest dir even if its mtime differs from that of the source device node and --times is given. Is this behavior expected? It seems to break the rule that a difference in preserved attributes disqualifies a hard link. To see the behavior, run the following as root: mkdir src dest basis mknod src/null c 1 3 sleep 1 mknod bas...

...e a script that dives into the user's directories and their maildirs. It looks like this: ============================================= #!/bin/bash for pad1 in $(ls /home) do if [ -e "/home/$pad1/Maildir/.Prullenbak" ] then find "/home/$pad1/Maildir/.Prullenbak/cur" -mtime +2 -type f -delete find "/home/$pad1/Maildir/.Prullenbak/new" -mtime +2 -type f -delete fi if [ -e "/home/$pad1/Maildir/.Allerlei.Spam" ] then find "/home/$pad1/Maildir/.Allerlei.Spam/cur" -mtime +2 -type f -delete find "/home/$pad1/Maildir...

https://bugzilla.samba.org/show_bug.cgi?id=12742 Bug ID: 12742 Summary: a proposal: fix bogus nanosecond mtimes on transfer (patch included) Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core Assignee: wayned at samba.org R...

If Maildir storage is used, the mtime of a given Maildir file is set to the message's INTERNALDATE. Now, when a client APPENDs a message to an IMAP mailbox, the client may optionally specify the INTERNALDATE: | If a date-time is specified, the internal date SHOULD be set in the | resulting message; otherwise, the internal date of...

Hello, I'm using rsync as part of a centralised config management for several servers. I'm trying to monitor the mtime of a particular directory and confirm that the remote copies are approximately as new as the the local master. However, mtime on that directory is not being synced. Here's my rsync command: cd $confdir && rsync -avpzR --checksum -I -e "ssh" --exclude='old/' ./* user...

On the wiki: http://wiki.dovecot.org/Plugins/Zlib I think there should be a step 5.0. along the lines of "get and remember the original message file's mtime" And a step 5.4 like "Using the touch command or some other method, set the now compressed message's mtime back to the mtime of the original message file." To preserve the message's internal time in case the indices ever get rebuilt. Does this sound right?

...tterly useless without it. On 09/07/2015 11:10 PM, Andrej wrote: > On 8 September 2015 at 13:57, Kevin Korb <kmk at sanitarium.net> > wrote: Hi Kevin. > > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> The ctime will always be newer or the same as the mtime. This >> is because changing the mtime also changes the ctime as does >> other things like changing the permissions. >> >> Rsync only pays attention to the mtime because rsync can set a >> specific mtime (--times) but setting a specific ctime is >> impossible...

Hello List, How would i rsync all files which are older than X-Days? I am missing some kind of -mtime option. Since this is quite common for backups i am wondering how you are doing this kind of stuff. Thanks, Mario

...onizing these files requires the use of --checksum or --ignore-times options, which are both sub-optimal in most cases (see caveats below). I would like to propose new options to efficiently synchronize these files. To make this report as clear as possible, I kindly remind that modification times (mtime) can be manually set by users (e.g. with touch) and rsync will preserve those during synchronization (with -a, which includes -t). By contrast, change times (ctime) are automatically updated by the OS when files are changed. rsync relies on modification times to decide whether it should skip or tra...

...30 06:26:18 2002 +++ samba-2.2.7a-fixed/source/client/clitar.c Thu Dec 19 15:50:20 2002 @@ -45,10 +45,10 @@ struct file_info_struct { - size_t size; + SMB_BIG_UINT size; uint16 mode; - int uid; - int gid; + uid_t uid; + gid_t gid; /* These times are normally kept in GMT */ time_t mtime; time_t atime; @@ -125,11 +125,11 @@ int blocksize=20; int tarhandle; -static void writetarheader(int f, char *aname, int size, time_t mtime, +static void writetarheader(int f, char *aname, SMB_BIG_UINT size, time_t mtime, char *amode, unsigned char ftype); static void do_atar(char...

...regular Mode: 0644 Flags: 0x0 Generation: 3550218717 User: 0 Group: 0 Size: 102400 File ACL: 0 Directory ACL: 0 Links: 1 Blockcount: 208 Fragment: Address: 0 Number: 0 Size: 0 ctime: 0x4165bae1 -- Thu Oct 7 17:53:37 2004 atime: 0x4165bade -- Thu Oct 7 17:53:34 2004 mtime: 0x4165bae1 -- Thu Oct 7 17:53:37 2004 BLOCKS: (0-11):453994-454005, (IND):454006, (12-13):454007-454008, (14-24):455201-455211 TOTAL: 26 Inode: 209219 Type: regular Mode: 0644 Flags: 0x0 Generation: 3550218717 User: 0 Group: 0 Size: 102400 File ACL: 0 Directory ACL: 0 Lin...

https://bugzilla.samba.org/show_bug.cgi?id=13385 Bug ID: 13385 Summary: rsync sometimes silently transfers more or fewer mtimes than it should Product: rsync Version: 3.1.3 Hardware: All OS: Linux Status: NEW Severity: regression Priority: P5 Component: core Assignee: wayned at samba.org Reporter: silvanschmitz at g...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The ctime will always be newer or the same as the mtime. This is because changing the mtime also changes the ctime as does other things like changing the permissions. Rsync only pays attention to the mtime because rsync can set a specific mtime (--times) but setting a specific ctime is impossible as it would violate the basic *nix security model. The...

...me, as the last observation is taken after 6 days ( and not 2 as the others). This is the code I'm using: library(nlme) DO<-c(0.107,0.118,0.271,0.431,0.597,0.909,1.259,1.688,2.301, 0.107,0.150,0.200,0.325,0.425,0.641,0.860,1.329,1.780, 0.101,0.159,0.204,0.484,0.663,1.019,1.335,1.880,1.927) mtime<-rep(c(seq(1,15,2),21),3) Subject<-rep(1:3,each=9) dataset<-data.frame(DO=DO, mtime=mtime, Subject=Subject) Joy <- groupedData( DO ~ mtime | Subject, data = dataset) m0<-nlsList( DO ~ SSlogis(mtime, asym, xmid, scal), data = Joy) m1.nlme<-nlme(m0) m3.nlme<-update(m1.nlme,rando...

If I run this: find /path/to/files/ -type f -mtime -2 -name *.xml.gz I get the expected results, files with modify time less than two days old. But, if I run it like this, with the print0 flag: find /path/to/files/ -print0 -type f -mtime -2 -name *.xml.gz I get older files included as well. Anyone know why?