similar to: --relative, --dirs and --delete without --recursive

I saw libxml2 have a security update on https://rhn.redhat.com/errata/RHSA-2012-1288.html. But centos only update libxml2 for centos 5., it also affect centos6. Centos already update ppid(RHSA-2012:1269), looks like libxml(RHSA-2012:1288) skiped.... Any explanation?

Dear R experts, I just upgraded R from 1.8.1 to 1.9.0 version. My .First() function in ~/.Rprofile contains x11() and par() functions. .First <- function() { x11(display = "", 8.0, 5.0) par(las = 1, ...) ## ... } And, R claims now, on startup: [hello messages skiped ...] Error in .First() : couldn't find function "x11" > I commented

On Wed, 28 Sep 2016 10:09:28 -0300 Gilberto Nunes via samba <samba at lists.samba.org> wrote: > Thanks.... I hope this is my last post with this matter! I hope it's your last post on any matter. You quit Samba very noisily. If you don't remember doing so, just look at the subject line. Don't look back. Go to your beloved Windows CIFS. You've found somebody better:

After fixing nested () problem manual run nighttest finished successfully with one remarkable logged problem: INITIALIZED CVS Root = :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm BuildDir = /home/wanderer/pkg/build/llvm/night/build WebDir = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD Prefix = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD/2004-09-06

Hi, I have several time series that I need to plot on the same plot. There are 3 problems with these series: 1. they do not start or end at the same times 2. they have different time intervals (seconds, minutes or hours) 3. they all have random missing time steps of a few step to longer periods of several days The data is imported from a database as POSIXct so that the first column holds the

rsync-2.6.6 manpage says: --delete [...] This option has no effect unless directory recursion is enabled. True. In fact, I noted that --delete doesn't delete anything if --dirs is used rather than --recursive. Is there any reason for --delete not to delete when used with --dirs? Is there a way to get rsync to actually delete files on the receiving end when using

rsync (2.5.[67]) --delete fails on dirs with the w bit cleared. (example below) Rsync will sync a dir with w bit clear, but will not remove it with --delete. This is not a big problem, but it will create situations where there are 'orphaned' files. Has anyone else had this problem? It looks like a change would be needed in robust_unlink (util.c). This function would have to do a chmod

Hello everyone, i try to use Samba RODC(4.6.5) with W2K8R2. Windows AD has around 35000 objects. My Samba machine is small one (ARM 32bit CPU) with only 2GB physical memory, so i can’t join to the domain because of expensive memory usage. To solve this Problem, i decide to replicate only critical objects and then let samba_kcc to get other objects. 1 ) Is this an possible way to use Samba AD or

Hi all, I ran into a weird corner-case of list.files today and I'm wondering what people think about it and a potential wishlist enhancement related to it. Consider the case where we call list.files with recursive and include.dirs both TRUE and we supply a pattern. In this case pattern is applied to directory names when deciding whether to list the directory return value but NOT when

Perhaps this could work: 2016-09-28 17:18 GMT-03:00 Gaiseric Vandal via samba <samba at lists.samba.org> : > I think there was a web app called SWAT. The problem I have with the > samba web app or gui config tools (I think redhat had one) is that they > might delete any fine tuning you set in smb.conf. > > > > > > > > > On 09/28/16 16:01, Steve Litt

On Wed, 2015-03-25 at 18:48 +1100, Damien Miller wrote: > Our ability to influence people who run truly obsolete software is > extremely limited. +1, mostly because those who still use something that outdated in their products are either dead, or simply don't care about their customer's security (which is typical in the embedded devices area). Just by us (or anyone else) saying

Protocols and ciphers are sunsetted all the time, this is a regular thing, but there are announcements before breaking changes are inserted. You assume people are slow to update anyway; some are, some aren't, what you're doing is wildly rewarding the slow updaters and punishing the fast ones. That has negative effects elsewhere. What would it hurt to announce the release in 3-6 months

Hello, i habe an Sama 3 Server with some shares. If I access these shares from Windows and if I generate new files or dirs with german umlaute everythink is OK. I can open theses files and I can open the directory. If I want do delete or rename the files or dirs with german umlaute I got an error message. "I can not read the file from source". creating new dirptr 256 for path

https://bugzilla.samba.org/show_bug.cgi?id=13920 Bug ID: 13920 Summary: --max-delete and dirs being replaced by symlinks on source Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayne

In can_extents we test whether the VDDK function VixDiskLib_QueryAllocatedBlocks works before declaring that extents are supported. This VDDK function can fail in several ways but most notable if the server doesn't support querying extents. In this case VDDK raises an error message through the error_function callback, which we turn into a call to nbdkit_error. In most cases this will cause

I was told that my earlier submission of this report contained a user-hostile attachment (courtesy of Outlook), so here it is again, with the log included below. The problem: Files that exist only on the remote system are deleted silently (i.e. not logged), rather than noisily as implied by the recommendation of --dry-run in the rsync man page definition of --delete to see what would be

https://bugzilla.samba.org/show_bug.cgi?id=3543 Summary: [ACL] rsync calls default_perms_for_dir on omitted implied dirs before ensuring they exist Product: rsync Version: 2.6.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Dear rsync people (particularly Wayne), I think it would be helpful for the options in the man page to be divided into sections based on which aspect of rsync's behavior they affect. Each section could also document rsync's default behavior when none of the options are given. Collecting all the possibilities for each aspect of rsync's behavior in one place would make it much easier

Patch includes fixes to man page including: - Typos/Spelling - Clarity - Special characters. - Moved around text explaining example. Make sure I didn't confuse the exclude list/file paragraph (line ~961 after applying the patch), I haven't used the feature and the motive of that paragraph is a tad unclear. Hope the patch is helpful. Never had used yodl before. Thanks for rsync. /a

Hi all, I have been using rsync to copy multiple dirs, eg: rsync -aR dira dirb /tmp Now, I no longer want to copy dirb, and I want it to be removed on the remote side, and I cannot figure how to achieve this. I tried: rsync -aR --exclude=dirb --exclude-deleted dira dirb /tmp but this has no effect. I have searched for similar posts, and found: