search for: modifications

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [root@divide mdonada]# smbldap-populate Using builtin directory structure adding new entry: dc=auroraalimentos,dc=com,dc=br failed to add entry: modifications require authentication at /usr/sbin/smbldap-populate line 389, <GEN1> line 2. adding new entry: ou=Users,dc=auroraalimentos,dc=com,dc=br failed to add entry: modifications require authentication at /usr/sbin/smbldap-populate line 389, <GEN1> line 3. adding new entry: ou=Groups,dc=aurora...

...) entry dc=gruporesasco,dc=local already exist. entry ou=People,dc=gruporesasco,dc=local already exist. entry ou=Groups,dc=gruporesasco,dc=local already exist. adding new entry: ou=Machines,dc=gruporesasco,dc=local failed to add entry: modifications require authentication at /usr/sbin/smbldap- populate line 499, <GEN1> line 22. adding new entry: ou=Idmap,dc=gruporesasco,dc=local failed to add entry: modifications require authentication at /usr/sbin/smbldap- populate line 499,...

When a file of same length already exists at the destination then the command 'rsync --archive --size-only' (--archive is same as -rlptgoD) may change the modification time of the destination file even if no modification was made. Type the following commands in a terminal in order to reproduce the problem: $ mkdir source $ mkdir target $ echo "file one" > source/file $

Hello, I have a question about how/why rsync updates modification times, which I haven?t been able to find an answer to. I have two locally connected storage devices running TrueNAS Core: one is new and empty, while the other is filled with files. When I run the following rsync command: rsync -avPh --itemize-changes --stats "${@}" to transfer files from the full storage to the empty

You are using rsync -a which copies (preserves) the timestamp. Meaning that rsync will copy the file then back-date it to the timestamp of the source file. Most copying tools do not do this though cp's -a does it too. Note that your itemized output says that the timestamp is different meaning that the file has changed since rsync last ran. Without the -a (or the included -t) the

Recently, our backup software oddly decided to rebackup a good portion of our file server instead of just doing an incremental. When I examined various sets of presumably identical files, I discovered that the modification dates on these files were no longer the same. Many files were re-dated to exactly one hour later such that if a file had been modified on 3/24/04 at 2:24:53 PM, it's

Hi Kevin, The -a flag in this instance is not back-dating the timestamp of the copied file to the source file. It is modifying it to the time of transfer and leaving it that way. Then any time I rerun that command it always updates the timestamp since it is always making it the time of transfer. I have a source file the has a modification date of 2015 and when I rsync it to day with -a the copied

That isn't how rsync should work with -a. Is something preventing it from backdating the file? What is the filesystem? Can you try copying your 2015 file with cp -a? On 10/9/24 14:56, McDowell, Blake wrote: > Hi Kevin, > > The -a flag in this instance is not back-dating the timestamp of the > copied file to the source file. It is modifying it to the time of > transfer

Hi all I have a problem where notification about file modification (edited text file) is not passed from one Windows7 to another Windows through Samba. Monitoring is done via custom application that recursively watches for all events on certain directory watchfolder. Strangely all events are passed through fine in watchfolder itself (including file modification). Also all other events like file

Hi My code is as following: #include <R.h> #include <Rinternals.h> //* the Projector part *// void Projector(double *L, int *dimL, double *G, int *dimG, double *W, int *dimW, int *xymod, int *dimxy, double *modif, int *dimif, double *Lsum) { ...} //* the interface part *// #define getDim(A) INTEGER(coerceVector(getAttrib(A,R_DimSymbol), INTSXP)) SEXP Projector5(SEXP L, SEXP G,

How do I transfer just the modification times with rsync? I now the file content is the same but the modification times are different. Is there a way to do this? Every way that I have tried causes the whole file to transfer as well. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

Whenever you use --times (included in --archive) rsync will fix incorrect time stamps. The only thing --size-only is doing is keeping the incorrect data instead of replacing it. The purpose of these options is to "fix" a copy done in a way that did not preserve timestamps but the data is known to have not changed. These options allow rsync to correct the incorrect timestamps without

Thank you! I run --times when I use rsync (I actually use the -a flag) but the times do not transfer over and if I run rsync dryrun with -i I can see that it wants to transfer the files because of times. When I run rsync a second time with your suggestion the times do transfer over. I don't know why... B ________________________________________ From: rsync [rsync-bounces at lists.samba.org]

In order to get the Oneac UPS (models ON700XAU, ON1000XAU, ON1500XAU) to work with NUT, I had to make a few minor modifications to the oneac driver. I've attached a patch with all the modifications. I tried to ensure that my modifications would not break any existing functionality, but I could not be sure without a legacy Oneac UPS to test against. In my investigation, I found out that the ONEAC Serial Interface scans...

...kind of post-link modification are you expecting?* > > The first thing that comes to mind is strip command which removes debug > info and symbol table. But it looks like you are expecting more than that? > > *Is computing memory-mapped sections strong enough to detect post-link > modifications?* > > I wonder if there's some section or an ELF header field that does not > mapped to memory at run-time but affects how the loader works. If such a > thing exists, computing a hash of all memory-mapped sections is not enough > to catch post-link modifications. > > On Thu...

How exactly does rsync determine that the copy has the incorrect timestamp and not the source file? Does it assume that the copy must be incorrect or are there other criteria that have to be considered? Quoting Kevin Korb via rsync <rsync at lists.samba.org>: > Whenever you use --times (included in --archive) rsync will fix > incorrect time stamps. The only thing --size-only is

Helo I have a big problem with samba and windows 2003 ads. I have a DC in win 2003 and centos4.3 with samba ADS. Registration of samba in ads has gone well , kinit gives no error and also net ads join worked well I can access shares based on the user in my DC, I am not using ACL, only the permission in the system and DC. My problem can be described in the following way. - getent

Hi. I have to make some minor modifications to the text.tree function - I don't like the way it prints the split labels (they are too long in my case and overlap). I tried to make s simple modification to the text.tree function so that it will limit the number of significant digits in tree labels, but could not - the original function us...

Hello list, is there any way to retrieve the last modification time from a Xapian::Database object? TIA Ralf Mattes -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL:

Greetings, I just upgraded from 2.2.3 (or whatever Debian stable has) to 3.0.4 (using the Debian packages available via the Samba mirrors). I'm running it on Debian GNU/Linux stable x86, kernel 2.4.25. I noticed that whenever I open a file using a Windows (I'm using Windows 2000) application, Samba changes its modification time to the current time. The old modification time is restored