search for: olddirs

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

Hi there, I've had a look on the web, and in the archives, but I dont see any mention to this problem/feature. Essentially, I have a local mirror, and a live webserver, with a little script that will execute a --dryrun rsync, ask the user for confirmation, then go ahead and transfer the local updates to the live server. The problem Im having is when Im sync'ing newly generated

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 I am sure the answer here is really easy but i am stuck! # mount | grep data | awk '{print$1,$2,$3}' gives me the info i require locally, however i need to execute this over about 1000 hosts so i run things remotely using ssh something like # MOUNTER=`ssh $i 'mount | grep data | awk '{print$1,$2,$3}''` however this fails as at the end of the line there are 2 ticks

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

Dear all, To create a *.pdf file from a *.Rnw file I do: olddir <- getwd(); setwd(outdir); tryCatch({Sweave("QAReport.Rnw"); tools::texi2pdf("QAReport.tex", clean=TRUE) }, finally = setwd(olddir) ); This works fine, however 'clean=TRUE' does only work when: outdir <-

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

Hi, I'm running version 1.2.15 (so no doveadm) with around 6000 maildir users, some of which are very large. For completeness, the details of the setup are as follows: - The maildirs are stored via NFS. - The indexes are on a volume local to the dovecot server. - Only one IMAP server currently. - A separate sendmail/procmail server delivers via NFS. I recently wrote the attached script

In my .Rprofile I have the following functions which display the current directory in the main R window title bar, and modify base::setwd() to keep this up to date. I like this because I can always tell where I am in the file system. cd <- function(dir) { base::setwd(dir) utils::setWindowTitle( short.path(base::getwd()) ) } short.path <- function(dir, len=2) { np

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

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) When I filed this a few minutes ago, I left off the rewritten read.ssd(). I've included it at the end this time. read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member

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

Greetings - Ok, I made a mistake that I need to fix. Fortunately it is not a destructive mistake, but I need some advice on how to correct the problem. CentOS 6.3 host system named Earth I was creating some new logical volumes within my exiting volume group for a new virtual machine using the LVM GUI. When I created the LV that I plan to use for root partition of the new VM (Bacteria) I

Running into problems configuring different locations for the volatile and other database directories. Can someone provide a quick sanity check on what I'm doing below? Thank you. Given [database] volatile database directory = /var/cache/dbdir/volatile persistent database directory = /var/cache/dbdir/persistent state database directory = /var/cache/dbdir/state And given, [root

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 subject about says it all. should this only be done once per device or periodically? thanks! - -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 Admin: Linux StepByStep - http://www.linux-sxs.org and http://jobs.linux-sxs.org Illiterate? Write for help! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux)

Am 14.05.2018 um 21:08 schrieb Reindl Harald via samba: > Am 14.05.2018 um 20:56 schrieb Carlos via samba: >> /opt/samba/var/log.samba >> >> { >>   rotate 10 >>         daily >>         compress >>         dateext >>         size 100M >>         nomail >>         missingok >>         notifempty >>         create 644 root

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

https://bugzilla.samba.org/show_bug.cgi?id=3392 Summary: fuzzy misbehaving if source is a file Product: rsync Version: 2.6.6 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: egmont@uhulinux.hu

Dear All, Currently i am using CentOS 4.4 Linux Logrotate is not happen without -f option I have executed the following logrotate /etc/logrotate.conf manually and Logrotate command exit without any error messages If i executed with -f option then Logrotate will happen I am not sure why this is happening. Can some one throw light on this. Regards -S.Balaji

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