similar to: atimes+ctimes patch

Displaying 20 results from an estimated 1000 matches similar to: "atimes+ctimes patch"

2014 Sep 22
0
Re: [PATCH] New APIs: Implement stat calls that return nanosecond timestamps (RHBZ#1144891).
On Monday 22 September 2014 13:48:38 Richard W.M. Jones wrote: > The existing APIs guestfs_stat, guestfs_lstat and guestfs_lstatlist > return a stat structure that contains atime, mtime and ctime fields > that store only the timestamp in seconds. > > Modern filesystems can store timestamps down to nanosecond > granularity, and the ordinary glibc stat(2) wrapper will return these
2014 Sep 22
2
[PATCH] New APIs: Implement stat calls that return nanosecond timestamps (RHBZ#1144891).
The existing APIs guestfs_stat, guestfs_lstat and guestfs_lstatlist return a stat structure that contains atime, mtime and ctime fields that store only the timestamp in seconds. Modern filesystems can store timestamps down to nanosecond granularity, and the ordinary glibc stat(2) wrapper will return these in "hidden" stat fields: struct timespec st_atim; /* Time of last
2006 Jan 24
1
propagate atimes with rsync-2.6.6 (fwd)
Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access
2004 Apr 10
0
patches for copying atimes
Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I
2008 Jan 05
1
OT: ctimes
I am going to convert my 32-bit Debian system to a 64-bit Debian system today. But, after I move my maildir files over to the new hard drive the ctimes are going to get modified to current time and mess up my automatic purge scripts for the Deleted Items folders. Is it possible for me to either keep the existing ctimes or is it possible for me to modify the ctimes to the date headers of the
2008 Aug 24
1
mtime, atime, ctime
Hello I am making backup of a Plesk Debian server to /backup using Rsync. My questioin is how can I preserve the ctime, mtime, and atime of original files? Thanks
2013 Oct 25
2
btrfs send/receive do not keep inode ctimes
Hello insiders is there low level support to change inode ctimes somehow? (on ext[234] it can be done using debugfs) It would be nice to make received snapshots as similar as possible to their send source. (I am not talking about uuids and such, just ls -lc output) creative ideas are welcome, Karl -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body
2008 Mar 04
1
preserve ctimes of *unchanged* directories on receiver
'rsync -a' updates the ctime on a directory even if no file in that directory has changed. A kind of workaround is to use '-O', but then the mtimes of directories are not preserved. (Usage example where this is important: maintain a copy of filesystem A in filesystem B, and use filesystem B as the source for incremental backups (e.g., with star). rsync is run before an
2006 Jan 10
1
bin/91622: /bin/cp does not update atime of the source file
On Wed, 11 Jan 2006, joe wrote: >> Environment: > RELENG_4 20051028 >> Description: > [cp fails to update atime] > > this occurs regardless of whether or not the user has > rwx permissions on the source file. does not apply of > course if the source filesystem is mounted read-only. > they are read-write here. > > since the source file is indeed being read,
2008 May 18
1
compile troubles - stat.mtim - 1.1hg
having trouble compiling dovecot-1.1hg latest pull I'm amost thinking _GNU_SOURCE needs to be defined as its built to work Any suggestions welcome. make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage/list' Making all in index make[4]: Entering directory
2016 Nov 10
0
[PATCH 2/3] qemu: Implement virtio-pstore device
On Fri, Sep 16, 2016 at 07:05:47PM +0900, Namhyung Kim wrote: > On Tue, Sep 13, 2016 at 06:57:10PM +0300, Michael S. Tsirkin wrote: > > On Sat, Aug 20, 2016 at 05:07:43PM +0900, Namhyung Kim wrote: > > > Add virtio pstore device to allow kernel log files saved on the host. > > > It will save the log files on the directory given by pstore device > > > option.
2017 Apr 13
0
[Bug 12742] New: a proposal: fix bogus nanosecond mtimes on transfer (patch included)
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
2004 Apr 20
1
improved atime patch
I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?
2015 Apr 24
2
Real sh? Or other efficient shell for non-interactive scripts
Pete Geenhuizen <pete at geenhuizen.net> wrote: > Initially Bourne was used because it was typically a static binary, > because the boot process didn't have access to any shared libraries. > When that changed it became a bit of a moot point, and you started to > see other interpreters being used. When dynamic linking was intruduced in 1988, people did kno know what we
2015 Apr 27
2
Real sh? Or other efficient shell for non-interactive scripts
<m.roth at 5-cent.us> wrote: > Ah. I don't remember if I was using csh, or ksh, and didn't realize about > bash. I *think* I vaguely remember that sh seemed to be more capable than > I remembered. If you like to check what the Bourne Shell did support in the late 1980s, I recommend you to fetch recent Schily tools from:
2017 Apr 09
0
failed to set times on ... Invalid argument (22) and what to do with it
Dear All, Along with the files that suddenly disappear, we have a bit of a problem with these that do not. Namely, in my test runs I can see a small but stable set of files, that rsync is repeatedly trying to transfer, and then repeatedly fails to updates their times ; and then the story repeats itself. The situation is illustrated by the log snippet below, where I have changed file names to
2008 May 30
3
v1.1.rc6 released won't compile
I got a compile error with rc6, rc5 works fine. amd64:dovecot-1.1.rc6# uname -a FreeBSD amd64.objtech.com 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #3: Fri Apr 18 02:18:13 EDT 2008 ./configure \ --prefix=/opt1/dovecot \ --localstatedir=/var \ --without-shadow \ --without-cyrus-sasl2 \ --without-pop3d \ --without-gssapi \ --disable-ipv6 \ --disable-debug \ --with-ioloop=kqueue \ --with-ssl=openssl
2020 Sep 27
1
strange crash with md5p8.diff + xxhash
With rsync-patches/md5p8.diff and --enable-xxhash % gdb --args ./rsync --version Using host libthread_db library "/lib64/libthread_db.so.1". rsync version v3.2.3-29-ge55788bd protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
2013 Oct 09
0
[PATCH 1/1] Porting klibc to AArch64
Details of the changes in second patch set as outlined in the first mail of this series: -------------------------------------------------------------------------------------------------------------------------- diff --git a/usr/include/arch/aarch64/klibc/archconfig.h b/usr/include/arch/aarch64/klibc/archconfig.h index 5cc1e7e..5ee278d 100644 --- a/usr/include/arch/aarch64/klibc/archconfig.h +++
2011 Jan 21
0
btrfs RAID1 woes and tiered storage
I''ve been experimenting lately with btrfs RAID1 implementation and have to say that it is performing quite well, but there are few problems: * when I purposefully damage partitions on which btrfs stores data (for example, by changing the case of letters) it will read the other copy and return correct data. It doesn''t report in dmesg this fact every time, but it does