similar to: Permission denied while running rsync as Superuser

Please advise on rsync usage. --delete doesn?t work without recursion(--recursion). The recursion is causing huge overheads for me. My directory trees are huge. Any suggestions through which I can cut overheads. It used to work well in rsync-v2.5.5 /opt/rsync-v2.5.5/bin/rsync --delete --checksum -lptgoD --rsync-path=/opt/rsync-v2.5.5/bin/rsync --hard-links --timeout=5184000 --exclude=.snapshot

I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to work or should I be able to upgrade one server at a time, test it, and move on to the next server? Or should I upgrade the domain controller first, then upgrade the member servers one at a time? I've tried to upgrade

At 07:02 AM 11/4/2004, samba-request@lists.samba.org wrote: >Date: Thu, 4 Nov 2004 14:01:17 +0300 >From: ds_shadof@uni-altai.ru >Subject: Re: [Samba] WINS setup / browsing >To: samba@lists.samba.org >Message-ID: <5791722390.20041104140117@uni-altai.ru> >Content-Type: text/plain; charset=us-ascii > > >Thursday, November 4, 2004, 2:15:55 AM, you wrote: >

I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to work or should I be able to upgrade one server at a time, test it, and move on to the next server? Or should I upgrade the domain controller first, then upgrade the member servers one at a time? I've tried to upgrade

I was able to resolve this issue. Just in case anyone is interested, I HAD to upgrade the PDC FIRST. Then I was able to upgrade the member servers without problems. ********************************************************* I am trying to upgrade our fully functional Samba domain from v3.0.2 to v3.0.7 or v3.0.8. My question is, do I have to upgrade every server in the domain in order for it to

I just successfully upgraded a server from v 2.2.8 to v3.0.7. When I execute smbstatus or swat it correctly shows v 3.0.7. When I browse thru network neighborhood it still shows v 2.2.8. I stopped samba, and removed /usr/local/samba/var/locks/browse.dat & wins.dat. Then restarted samba. It still reports v2.2.8 thru network neighborhood. In viewing browse.dat it shows 2.2.8. Where is this

Hello, I use rsync v3.0.7 with "--delete-during", but it appears to act more like "--delete-before". I've checked the docs and list archives, but I am still discovering some of the subtleties of rsync, and I can't see where I'm going wrong. There's an example of my issue below... can anybody set me straight? =-) o We archive a small number of large files,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, rsync v3.0.7 I am backing up data to a USB memory drive that is formatted FAT32, which does not comprehend linux permissions. I added the "--no-perms" option to the option set. rsync still attempts to change the permissions. OPTS = "--no-perms --archive --stats --delete --itemize-changes - --quiet

Hello all, forgive me if this is old news but it seems to me that smbclient is prone to getting into an infinite loop when mget'ting a stack of files. I have tested (compiled from source with defaults) samba versions 3.0.10, 11, 12, 13, 14, 14a Versions prior to 3.0.13 are fine, in my environment, versions 3.0.13 and later are causing the problem. The basic data on my system is -a P4 3.2

I have an odd use case where I need to get the Samba Client (SMBClient.exe) compiled for use on a Windows 2012 server to access another Windows 2012 Server through SMB. I have scoured the internet, posted to forums, and even emailed authors that have compiled older version of Samba with no luck. For example Lee Peckham complied just the client and posted it here:

Hello, I got this problem: I want to mount a directory without providing a login/password [indicaf$]. I thought that "guest ok = yes" would be sufficient. But it not works. What option is the right one to open a share to everyone without a login box in windows ? Thanks. This is my smb.conf (samab v3.0.7): tccwebcom# more smb.conf # Samba config file created using SWAT # from

Hi All, I implemented a standalone ruby program that helps to my RoR app to execute processes in background, the web app adds a request to the ruby program, then this spawns a thread and the web app monitors the status until the process is completed. All things work perfect and nice. But, I noted that I''m getting multiple DB idle connections, I think (not sure) this behavior is OK

Running under debian, using SAMBA V3.0.7, I use PASS=secretworld USER=joe (echo $PASS; echo $PASS) | smbpasswd -s -a $USER Note: smbpasswd requires a double typed in password, It took me a lot of minutes to figure that difference between earlier version and the 3.0.7 out but now it works. In perl scripts I use this commandline like #...somewhere in a for/while loop... my $cmd = "(echo

Running SuSE v9.0 and Samba v3.0.7. I have samba up and running ok with printer and file shares working peer to peer with Win2000 box. However, I would like to use SWAT for config purposes, rather than manual edit. If I run http://localhost:901 I receive a 'connection refused' error message. I had a look in /etc/services and see these two lines as the only ones referring to port 901:

On Thu, 2016-05-12 at 15:39 +0000, Allan P. Dynes wrote: > I have an odd use case where I need to get the Samba Client > (SMBClient.exe) compiled for use on a Windows 2012 server to access > another Windows 2012 Server through SMB. I have scoured the > internet, posted to forums, and even emailed authors that have > compiled older version of Samba with no luck. For example Lee

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 rsync v3.0.7 (also seen with 3.0.5) linux 2.6.34-12-desktop x86_64 os/2 v4.50 fp3 rsync makes an unusual error when building its file list for a transfer: it decided to move a directory further down the directory tree than where it was located in the source volume. Even more strange is that during the next run of rsync, it adjusts the *source*

Hi guys, I'm new to this mailing list as I just came across a small problem after installing the rsync package on one of our Solaris 10 machines. I installed rsync package SMCrsync v3.0.7 SPARC and although command man rsync worked, man -k rsync and whatis rsync did not despite the fact that I had run a catman -w to rebuild the windex databases. After reading the catman man page, I suspected

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, rsync v3.0.7 linux 2.6.37.6-0.20-desktop x86_64 Below is a log of a backup session. I do not understand why the "exclude=/data01/..." is being ignored. The session is started in a bash script. The actual text is: - --exclude='/data01/t-drv/websites/owncloud/data/sma-admin/' I guess rsync cleaned it up to suit itself.

https://bugzilla.samba.org/show_bug.cgi?id=10304 Summary: safe_read failed to read 1 bytes Product: rsync Version: 3.1.0 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: polhallen at fuckaround.org

Earlier this year I upgraded all of our Unix Solaris servers from Samba v2.2.8 w/no domain to Samba v3.0.2 w/one domain. I have been adding Windows 2000 and Windows XP workstations to the domain. Everything has been working fine. I run the winbindd daemon but do not have winbind "configured" in any other way other than these few entries in the global section of the smb.conf files on