similar to: Samba and Windows file timestamps

Derek -----Original Message----- From: Michael Wood [mailto:esiotrot at gmail.com]=20 Sent: Saturday, November 13, 2010 12:43 PM To: Derek Lewis Cc: samba at lists.samba.org; Jeremy Allison; = samba-technical at lists.samba.org Subject: Re: [Samba] Problems with ACL jumbo patch Hi On 10 November 2010 10:22, Derek Lewis <dlewis at mtu.edu> wrote: > Okay, I search the apt repositories

I have ACLs working for files with the following set in my share definitions: inherit permissions = yes inherit acls=yes map acl inherit=yes vfs_objects = acl_tdb While testing my Samba configuration, I found that permissions are being set to 'special' for directories being copied from Windows instead of the ACL being fully populated. Does Samba 3.6 fully implement ACLS, or are

Hi All, Can someone help me in getting info about specific dtrace features introduced in individual S10 updates like U1,U2,U3 etc... This message posted from opensolaris.org

I am upgrading a Samba 3.6 to 4 and wanted to keep my shares and files from the previous version. Will I be able to maintain file metadata in the switch? Sent from my iPhone

Hello, When I upgraded to dovecot (changing servers at the same time) in November last year I copied the maildirs from my old server without using the -p option to preserve timestamps! Since my mail client displays the email dates based on the Date header rather than the imap "internaldate" I didn't notice the problem until today when I tried to migrate an account to gmail using

I am interested in compiling Samba 4 and trying the advanced features. I followed the instructions on samba.org to build and compile, though I get the error: failed program.confdefs.h. I have run into this error before, and looking over config log, I see that the build does not see many of the dependencies. Can I modify the build to point to the required files, or at least trace the source

Two questions. First, timestamps seem to be getting screwed up when I access files on the company's NT server. Someone (using NT) creates some files. My ls -l output shows them as having screwed up dates (ie, 1935, 2027, etc). 95, 98, and NT users see the dates as normal. When I copy any files with cp, the dates change for me, although remain nonsensical, but now the timestamp is also

> I'm running samba 2.X on Solaris (2.6, 2.5.1), and SunOS 4.X (but don't > tell anyone about that last one). > > I had been running samba 2.0.3, and one of my users noticed that when he > copied a file, using an NT 4.0 workstation, copying a file from an NT > fileserver (NTFS) to a Samba filesystem, that the dates were wrong on > the copied file. In particular, any

Hi all, I have two vectors of data: The first vector contains timestamps (as integers), however the difference between these dates varies. For instance, the vector can be c(0, 5 , 10, 20, 25, 30) so that there is a "jump" between the third and the fourth element. The second vector contains the associated values that I want to plot against these timestamps. My problem is that I

I have timestamps from mysql database: > dput(tstamp) c(1225221868L, 1225221906L, 1225221906L, 1225230997L, 1225231000L, 1225231003L, 1225231152L, 1225231348L, 1225231351L, 1225231400L ) How to convert these into normal dates? Thanks, jrara

Matthew Chapman wrote: > When I mount a W95/98 drive and create or modify files, everything is > groovy. > > When I mount an NT drive and create, modify, or read files (as in, copying > them from the NT drive to my own local drive), the dates go crazy. > > Our sysadmin tells me the NT system is NT Server 4.0 Enterprise Eddition, > service pack 3. Hi, Matthew, I'am

>Date: Wed, 16 Oct 2002 14:26:46 -0500 >To: Wayne Davison <wayned@users.sourceforge.net> >From: Sean O'Neill <sean@seanoneill.info> >Subject: Re: HELP !!! Problem with file timestamps updating "weird" during >rsync data pull >Cc: rsync@lists.samba.org > >At 12:10 PM 10/16/2002 -0700, Wayne Davison wrote: >>On Wed, Oct 16, 2002 at 01:36:10PM

Hi all, I have the following problem: I have a csv-file consisting of timestamp values (no dates), e.g.: Timestamp1;Timestamp2; 05:24:43;05:25:05; 15:47:02;15:47:22; 18:36:05;18:36:24; 15:21:24;15:22:04; I need a vector with the difference of the two timestamps, so I read the data with the read.csv-function: myObj <- read.csv("file.csv",header=TRUE,sep=";"). I have then

On Wed, 26 Aug 1998, Matthew Chapman wrote: > > Two questions. First, timestamps seem to be getting screwed up when I > > access files on the company's NT server. Someone (using NT) creates some > > files. My ls -l output shows them as having screwed up dates (ie, 1935, > > 2027, etc). 95, 98, and NT users see the dates as normal. When I copy > > any files

> Date: Sun, 24 Jan 2016 15:43:20 -0800 > From: Wayne Davison <wayne at thedavisons.net> A couple questions below; please bear with me. > No, if you do a ext4 -> ext4 copy, rsync has set the matching ns info for > transferred files since 3.1.0. There was a case prior to rsync 3.1.2 where > a brand-new file transferred in the same second it was created

Dear all, I am having a matrix that stores data information in the following format. > roofPart1$TimeStamps[1:5,]      [,1] [,2] [,3] [,4] [,5]   [,6] [1,] 2011    7   21   15   25 20.609 [2,] 2011    7   21   15   25 23.265 [3,] 2011    7   21   15   25 26.000 [4,] 2011    7   21   15   25 28.671 [5,] 2011    7   21   15   25 31.343 I would like to be able to report some simple statistics

Running rsync 2.3.1, 2.4.1, and 2.5.5 on Solaris 8 on various system. I'm using rsync to pull data over for collecting performance data for graphing in Orca. What I'm seeing is the timestamps from time to time of the data files is being setup "weird" on the system the data is being pulled to. The timestamp should match that of the system the data is pulled from right ?

I am interested in compiling Samba 4 and trying the advanced features. I followed the instructions on samba.org to build and compile, though I get the error: failed program.confdefs.h. I have run into this error before, and looking over config log, I see that the build does not see many of the dependencies. Can I modify the build to point to the required files, or at least trace the

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?

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?