similar to: protocol errors when using --dryrun

Rowland, You could go another step further and run that with "notify" to monitor for changes, instead of having to run it in a cron job. In my experience, "notify" works using smbclient, but not so with libsmbclient. Another nice benefit of using smbclient + 'samba-tool ntacl sysvolreset' over rsync is that you don't need worry about the built-in user/group ID

Hi, in this thread: https://lists.samba.org/archive/samba/2019-July/224365.html Joachim Lindenberg reminded me that he was using smbclient to sync Sysvol. He posted (in the link above) a link to his original post: https://lists.samba.org/archive/samba/2019-July/224346.html Here he posted a copy of his script. I personally would never have thought about using smbclient, but it just goes to

When --partial-dir is used rsync creates new or updated files inside a temporary dir. For example the new version of some/path/file is created in some/path/<partial-dir-name>/file and later moved. What happens if a new directory is created? If some/path/newdir/newfile is to be copied, is it done in some/path/<partial-dir-name>/newdir/<partial-dir-name>/newfile? Or is newdir

https://bugzilla.samba.org/show_bug.cgi?id=7565 Summary: --check-point=<TIME> +options.c.patch +generator.c.patch Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

Currently, rsync --delete -avvn test1/ test2/ --existing will give output such as: not creating new file "newdir" not creating new file "newdir/newfile" not creating new file "newdir/subdir" It would make more sense if it said: not creating new directory "newdir" not creating new file "newdir/newfile" not creating new directory

Hi Bob, [CC: Amitay, who is better at SeLinux] On Wed, 4 Nov 2020 09:33:10 -0500, Robert Buck via samba <samba at lists.samba.org> wrote: > This turns out to be an SELinux issue. Does anyone know the proper commands > to restorecon or otherwise to set the SELinux policy for > persistent/volatile database files moved to a different directory? I'm not sure if you're asking

As you may have noticed I am looking into containers? in order to minimize configuration I also started looking into options for sysvol replication. I am aware of the list at https://wiki.samba.org/index.php/SysVol_replication_(DFS-R) Ignoring the robocopy option, essentially all of them use rsync, w/o ssh, w/o some extras like unison, osync, or lsyncd as Sven suggested, plus optionally defining a

I, too have been looking into alternatives to the rsync-based sysvol replication workaround, and really liked the idea of using the existing Sysvol SMB share, rather than a secondary protocol (with its own authentication, etc). When I realized that Andrew Bartlett was a primary developer of both Samba and Rsync, I was even more surprised that Rsync doesn't support an smb:// URL. csync [1] is

I thought this can be useful to someone, so here it goes. I am using automatic SysVol replication with the help of "watcher", a recursive incron. https://github.com/splitbrain/Watcher "Watcher is a daemon that watches specified files/folders for changes and fires commands in response to those changes. It is similar to incron, however, configuration uses a simpler to read ini

A patch that was applied yesterday tried to turn the vnc option off if dryrun was set. Unfortunately, the way it was actually coded turned vnc ON if dryrun was not set! I think this patch should fix it (someone who actually uses vnc & dryrun should test it, though). -George +-------------------+---------------------------------------- | dunlapg@umich.edu |

Don''t start VNC on a dry run. Signed-off-by: Arun Sharma <arun.sharma@intel.com> --- a/tools/python/xen/xm/create.py Tue Jun 21 19:12:48 2005 +++ b/tools/python/xen/xm/create.py Tue Jun 21 13:50:09 2005 @@ -618,6 +618,7 @@ config = opts.vals.config else: opts.load_defconfig() + opts.vals.vnc = not opts.vals.dryrun preprocess(opts, opts.vals)

On Wed, Jul 23, 2008 at 11:24:49AM +0200, Karel Zak wrote: > On Wed, Jul 23, 2008 at 04:43:30AM -0400, Christoph Hellwig wrote: > > On Wed, Jul 23, 2008 at 10:39:38AM +0200, maximilian attems wrote: > > > klibc mount has only short options thus uses the following syntax > > Frankly, it seems like a klibc problem... well not directly, but right klibc-utils should have

As I reported a while back rsync doesn't handle metadata (permissions and ownership) in dryrun mode. I offered to make a patch and that offer still stands. I didn't have the time for it until now and want to pick it up again. I had some ugly hack back then but I want to redo it in a clean way. I would like some input on my thoughts. IMHO, it would be ideally if the check for dry_run

~ ~ ~ ~ ~ rss:/etc # 358C written rss:/etc # man mount Reformatting mount(8), please wait... MOUNT(8) Linux Programmer's Manual MOUNT(8) NAME mount - mount a file system SYNOPSIS mount [-lhV] mount -a [-fFnrsvw] [-t vfstype] mount [-fnrsvw] [-o options [,...]] device | dir mount [-fnrsvw] [-t vfstype] [-o options] device dir

I was glad to see a new version of rsync because I though that it was kind of dead. :-) Anyway, I just checked and noticed that the following isn't fixed yet, or is considered a feature. When run in dry-run mode, rsync doesnt report diffs in permissions and ownership. IMHO this is not the expected and wanted behaviour, I want to see exactly what it would do without the '-n'. I have

From: Gene Cumm <gene.cumm at gmail.com> COM32: Add directory functions getcwd(), opendir(), readdir() and closedir(). This depends on the patch that I just submitted creating the COMBOOT API calls. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- The intention is to create the library calls with (hopefully) POSIX compliance such that a small application written to use these

From: Gene Cumm <gene.cumm at gmail.com> COM32: Add directory functions getcwd(), opendir(), readdir() and closedir(). This depends on the patch that I just submitted creating the COMBOOT API calls. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- The intention is to create the library calls with (hopefully) POSIX compliance such that a small application written to use these

Hi! Here is a patch against openssh-2.9.p2 that adds support for Maildir style mailboxes, the way which qmail prefers to store mails in. The changes/additions are the following: 1) $MAIL env. variable is set to $HOME/Maildir if it exists, or else to _PATH_MAIL/$USER. 2) Mail checking (the main purpose of this patch) is done by first checking whether $MAIL is a regular file or directory. If

From: Gene Cumm <gene.cumm at gmail.com> COM32: Improve opendir() to deal with no '/' at end of string Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Originally, this was going to be 3 patches but I ended up doing a little more. Currently, the COMBOOT call required a '/' to recognize that you're searching for a directory. This checks and automatically

rpeng@jhsph.edu wrote: > I get different behavior on Linux: > > system("mkdir newdir") > dir("newdir", all.files = TRUE, recursive = TRUE) ## R hangs The point is that all.files=TRUE implies returning also "." and ".."! Hence the recursion uses to be infinite (from "." to "." to "." ......). If recursiv = TRUE,