similar to: Preserving timestamps with smbclient

I have a backup script that uses smbclient to push files to a Windows server and I have noticed that the mtime on the server is the time of upload, not the mtime of the original file. I can not find an option to preserve the original mtime. Does such a thing exist? Shouldn't it do this by default?

We don't currently detect if a file with an old timestamp has been moved into a directory. This fixes that. --- lib/Sys/VirtV2V/Config.pm | 14 ++++++++++++++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git a/lib/Sys/VirtV2V/Config.pm b/lib/Sys/VirtV2V/Config.pm index 3fff455..bb30dae 100644 --- a/lib/Sys/VirtV2V/Config.pm +++ b/lib/Sys/VirtV2V/Config.pm @@ -154,6 +154,7 @@

The FAQ mentions how to configure nut to pass the power information to HAL so that gnome-power-manager can display it, but HAL has been depreciated and removed from Ubuntu since 2007. Has nut been updated to worth with UPower instead?

Hi, for some reason, all timestamp fields with or without time zone in my Postgres tables seem to be casted to nil. From console: >> me = User.find(''PS12345'') => #<User:0x2379788 @attributes={"mtime"=>"01.03.2006 13:26:32.737166", "valid"=>"8", "valid_from"=>"01.03.1999 14:09:21 CET",

Hi all, we observed a strange effect when copying an file within a samba share: Both atime an mtime of the target file are set to the mtime of the original file. The atime of the original file is updated to the current time. 1. Status of the original file: # stat test.txt File: `test.txt' Size: 3 Blocks: 8 IO Block: 4096 regular file Device: 811h/2065d

I have this code: Link.find(params[:id]).toggle!(''active'') Before it, its timestamp is: 2005-11-20 20:45:48.741973-07 After: 2005-11-20 20:45:48-07 Why does Rails take it upon itself to truncate the seconds fraction? How can I get Rails to not change it? Thanks, csn __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best

-------- --Multipart_Thu_Apr__8_13:33:51_1999-1 Content-Type: text/plain; charset=US-ASCII Hello guys, I always wondered why smbclient keeps timestamp in `put'ting a file but does not keep it in `get'ting a file. Alternative to keep the time stamp in `get'ting file is to use -Tc option or smbtar script, but they are a bit hairy for interactive use, and it can only dump files with an

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

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

Hello all. Our system consists of two linux machines, each running Red Hat 7.1 (kernel 2.4.9-34), using SMB to mount multiple shares hosted by a Windows 2000 Advance Server. smbclient from Samba 2.2.5 is used to do the actual mounting. Over the weekend, a number of files on these SMBFS shares were created with incorrect timestamps (modification times). In some cases, the timestamps were off by

smbclient (and smbtar) in version 2.2.7a (and prior) has problems with large files (> 4GB). The following patch (against 2.2.7a) fixes all known problems with this. This code has been checked into the CVS tree in all branches as well. -- ====================================================================== Herb Lewis Silicon Graphics Networking Engineer

Hi all, I'm one of the GNOME gvfs maintainers, and would like to improve the support of smb in gvfs, especially in the context of taking advantage of the improvements of SMB2 and SMB3. Currently we use libsmbclient which provides a fairly easy to use API. It is not, however, quite sufficient for the way that we would like to use it (at least I think so): - Slow transfer speeds. Based on a

Hello, A few days ago I posted a question about handling timestamps in rsync (Q: rsync - preserve timestamps, but not use it to define files to update), but did not get a single response, so I thought I'd rephrase it. Also, with a new release of rsync out, may be there is some more time that knowledgeable people have :-) So here it goes. I want to be able to do two things together: --

> On Aug 2, 2024, at 00:32, ilya Basin <basinilya at gmail.com> wrote: > > 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 SSH2_FXP_FSETSTAT for directories. It doesn't have a separate "touch" command to set mtime for a path and its

I am using outgoing call files. I typically see the "ooh something changed / timeout" on a regular bases every second to be exact. Then it stops until some other call event happens. So I "mv" my call file to the outgoing spool directory, I am listening to that message, another call file is "mv"'ed into the directory and something happens to the timeout that its

Hi, is it possible to update the modification time stamp of a file using R (on file systems supporting it)? It is sufficient to update the modification time to the current time. The best I can do for now is: touchFile <- function(pathname, ...) { if (!file.exists(pathname)) stop("No such file: ", pathname); info <- file.info(pathname); if (info$isdir)

Hi, apart from the mmap(2)ed DBM files that Samba uses, are they any cases where Samba will *modify* data files without setting the mtime ? I have issues with rsync not seeing changes to Samba exported files (md5sum don't match). The mtime is however in the very distant past (say 2004), but the content seems to have changed. I don't think it's a data integrity issue. Any idea ?

Hi there, i still have a weird problem with Powerpoint an Excel files stored on a Samba share. Only read on if you -use a samba share as MULTI-user file repository (no force_user etc.) -where multiple, different users share files in common directories -the modification time of a file is of any relevance to you. (seems like lots of folks don?t bother access rights or keep their information

On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: >I'm trying to clone a volume in a storage pool and I'm following the steps >described here: >http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html > >My code looks like: > > destXML = """ >

I'm trying to clone a volume in a storage pool and I'm following the steps described here: http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html My code looks like: destXML = """ <volume>