similar to: rsync and the file's mtime

I saw this in the archive: http://www.mail-archive.com/rsync@lists.samba.org/msg06880.html I'm having the same problem with samba hanging, except it's not very re-creatable. I have a script that runs rsync, sleeps for 30 seconds and runs rsync again. It hangs about once every 24 hours. The script runs a rsync push over ssh. I've been running the same rsync scripts for 18 months

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

https://bugzilla.samba.org/show_bug.cgi?id=5867 Summary: rsync with ACLs resets mtime on targets Product: rsync Version: 3.0.4 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: samba@byshenk.net

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would need to see both your existing rsync command line and the output of --itemize-changes when such an occurrence happens before I can really understand what is happening. In the end, if you have any output at all the bare minimum should be - --itemize-changes. --verbose is utterly useless without it. On 09/07/2015 11:10 PM, Andrej wrote: >

greeting samba.general; i am trying to set up a backup server to archive files from a windows 2000 fileserver, and i can't seem to get filenames containing non-ascii characters to appear correctly on the linux box. my windows server: windows 2000 service pack 4 my linux server: debian 3.1 kernel 2.6.13.3 with these options: CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set #

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

-----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.

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"

Hi all, using latest asterisk-svn I want to reflect an video call incoming via an PRI EuroISDN channel to another outgoing PRI channel, and I want the the outgoing channel to have the exact same bearer capability < Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Unrestricted digital information (8) < Ext: 1 Trans mode/rate:

I've googled / voip-info'd / searched until my eyes are blurry, but couldn't see the info I was looking for. I've turned here for help! Asterisk CVS head (9/7/04) Fedora Core 2 (updated to 2.6.6 kernel) DE405P (jumpers set to E1) I want to put asterisk in the middle of our current pbx (Meridian Option11) Currently the meridian has a 2MB pri EuroISDN card linked via a rj-45 into

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 archive on an exported gluster fs and

Hi. It seems that dovecot is using the current time, not a maildir file's mtime for INTERNALDATE when a message is re-indexed: $ cd Index $ rm -rf .INBOX $ cd ../Maildir/cur $ stat * File: `1392914632.P54451Q0M08633.smtpin01,S=2215,W=2249:2,' Size: 960 Blocks: 8 IO Block: 1048576 regular file Device: 36h/54d Inode: 11132959 Links: 1 Access: (0600/-rw-------)

I'm connecting to "EFT Server" https://www.globalscape.com/eft and it has an SFTP module. It has nothing to do with OpenSSH, but enterprise likes it for some reason. I don't control the server. Looks like EFT doesn't support SSH2_FXP_FSETSTAT (working with a file handle), but it does support SSH2_FXP_SETSTAT (working with a file path). OpenSSH sftp only uses

Hi, everyone! This is a follow-up to "Looks like a bug to me: Dovecot ignores Maildir/new timestamp" from Fredrik Roubert on 01.12.2015: https://www.dovecot.org/list/dovecot/2015-December/102585.html I've run into the same problem as Fredrik: When manipulating my Maildir locally with mutt, deleting a message from new/ doesn't cause a full update of the index. Therefore, IMAP

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?

Hi, I''m writing my requirements in rspec, however, I can not figure out a way to execute all specs according to alphabetical order, not by last modified time. According to the documentation, it seems like the default is by alphabetical order, I just can not get that to work. In the unit tests with the rspec package, seems like only mtime was tested. Can anyone tell me how to run specs

I'm really excited about the recent work on extended attributes. I've compiled 2.6.9 with xattr support, and run a few tests. It seems that if I have a file with an extended attribute ( a resource fork in this case), and I run rsync -aX , the mtime is not preserved. Example: stat xattrsrc/a 234881026 2894399 -rw------- 1 admin staff 0 1048576 "Nov 10 10:03:01 2006" "Nov

Hi, I''m writing my requirements in rspec, however, I can not figure out a way to execute all specs according to alphabetical order, not by last modified time. According to the documentation, it seems like the default is by alphabetical order, I just can not get that to work. In the unit tests with the rspec package, seems like only mtime was tested. Can anyone tell me how to run specs

samba on Raspberry pi 4b - Linux 6.1.41-v8+ aarch64 GNU/Linux if I do a mtime on the file that gets shared I see this Modify: 2020-10-22 09:02:16.991364753 -0400 when I do a mtime on the same file on the client (Linux) I see this Modify: 2020-10-22 09:02:16.991364700 -0400 Is not a big deal it just caused some rsync confusion that was addressed by using --modify-window=1 Is this by design

I've just tried that. It still fails. Is it possible to dump the decrypted sftp commands? I tried -vvv but found nothing interesting. The Total Commander plugin calls: libssh2_sftp_setstat(ConnectSettings->sftpsession, thename,&attr) What does the command line client use? -------- Original Message -------- From: Brian Candler [mailto:b.candler at pobox.com] Sent: