Dear Ladies and Gentlemen,
We are pleased to inform you, that our Gallery was updated.
Our Gallery was enlarged with new artists. There you can find paintings
from
Barabanova Anastasia, http://www.gallery-a.ru/painter.php?aid=091
Olenich Roman.http://www.gallery-a.ru/painter.php?aid=100
Also -
Hi,
I am exploring extending Kyle Jones' patch (which implements
post-transfer filter in receiver.c) to pre-filter or otherwise
pre-process the file before it is sent.
Kyle Jones patch can be found here
On Mon, Jul 07, 2003 at 11:42:04PM +1200, Martin Langhoff wrote:
Hi,
I am exploring extending Kyle Jones' patch (which implements
post-transfer filter in receiver.c) to pre-filter or otherwise
pre-process the file before it is sent.
Kyle Jones patch can be found here
i'm trying to use rsync to mirror my server boot volume to another
disk of the same size (120gb) on the same machine:
% sudo rsync -avxuH --delete --progress /./ /volumes/cbc.server2/
although all of the files from the source volume appear to copy to
the destination, if i try to boot from the
On Mon, Jul 07, 2003 at 10:20:29AM -0400, Tony Alexander wrote:
i'm trying to use rsync to mirror my server boot volume to another
disk of the same size (120gb) on the same machine:
% sudo rsync -avxuH --delete --progress /./ /volumes/cbc.server2/
although all of the files from the
Ah yes, I recall thinking that your patch should go in, but I thereafter
forgot about it. I've gone ahead and committed your change since it was
very simple and similar to what we used to do in 2.5.5, only with a
better heuristic. I'm planning to look into Thorild Selen's patch as--text
Hi Hardy:
Thanks for your comments. They are greatly appreciated.
I tried your suggestion regarding the UID and GID. I set them to
the owner and group of the /bak directory. Also I currently have
the permissions on the directory at 777. I killed and restarted
the server process and retried
Hello
Just copying does not make a disk a boot disk.
This needs a boot block to be added to the disk
Incase of a Solaris OS
type in the following
installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s0
(Example only)
-Sudar
-Original Message-
From: [EMAIL PROTECTED]
Hugh, I did a quick test with 2.5.5, and here's what made it
work for me - the 'read only' parameter. Here's my daemon
/etc/rsyncd.conf file:
log file = /var/log/rsync
# this is a comment
[rsync-test]
uid=test
gid=test
read only=no
path=/test_rsync
it didn't work
On Mon, Jul 07, 2003 at 06:29:58PM +0200, Thorild Selen wrote:
It's not enough just checking the last char to see whether something
is an address: [...]
Yeah, good point. I've checked in an improved version of the test based
on your suggestions (which I finally got around to looking at in
Hi Hardy:
Nice catch - I missed that one when I reviewed the man page.
Unfortunately it made no difference. I have also tried moving
the module params from the global section to the module section
but that also made no difference - exactly same messages.
Just to keep things straight, here is my
Wayne Davison writes:
My patch leaves out the IPv6 logic if INET6 is not configured into rsync.
Sounds reasonable.
I've checked-in the appended patch. See if you like it.
Looks good to me. I'll report to the Debian bug tracking system that
these issues are now fixed in CVS upstream.
On Fri, Jul 04, 2003 at 12:17:43PM -0700, Hugh E Cruickshank wrote:
hosts allow = fisdev pgiprd
Each of these names needs to be either a fully-qualified hostname, a
wildcard expression that matches a fully-qualified hostname, an IP
address, localhost, or some combination thereof. E.g.:
hosts
Ok, I think I've got it narrowed down.
1) First, comment out both 'hosts allow' and 'auth users',
save it, kill and restart the rsync daemon, and try your
rsync again. Hopefully that will work.
2) Uncomment the 'hosts allow' line, save, kill and
restart daemon, and try rsync again - you will
On Mon, Jul 07, 2003 at 03:38:15PM -0400, Hardy Merrill wrote:
[...] kill and restart the rsync daemon, and try your rsync again.
I've noticed that it's not necessary to kill and restart the rsync
daemon to get it to honor changes to the rsyncd.conf file. FYI.
..wayne..
--
To unsubscribe or
Hi Wayne:
You are correct. This did make a difference but did not resolve the
problem. See my previous response to Hardy Merrill's message.
Thanks, Hugh
--
Hugh E Cruickshank, Forward Software, www.forward-software.com
From: Wayne Davison Sent: Monday, July 07, 2003 12:36
On Fri, Jul 04,
Hi Wayne:
That's good to know. I thought that it might be the case (as it is
with SAMBA), but I did not see anything obvious in the man pages
(that or I am blind - always a good possibility).
Regards, Hugh
From: Wayne Davison Sent: Monday, July 07, 2003 12:44
On Mon, Jul 07, 2003 at
If anyone else has any ideas, please chime in, as I'm
getting to the end of my list of things to try. The
server is a SCO box and the client is a RH8 box.
Hugh, let's go back to the beginning - in your first
message, you stated:
---
In the above example fisdev is an SCO
Hi Hardy:
I had originally setup 2 rsync servers one on SCO OSR5 (fisdev, our
development server) and one on RH8 (pgiprd, our production server).
During my initial tests I tried using both fisdev as the server with
pgiprd as the client as well as pgiprd as the server with fisdev as
the client.
On Tue, Jul 08, 2003 at 07:45:00AM +1200, Martin Langhoff wrote:
I have seen Kyle's approach of handling the forking directly, and I know
I cannot handle that level of complexity. Using something like popen (I
am using
http://www.gnu.org/manual/glibc-2.2.3/html_chapter/libc_15.html as
On Mon, Jul 07, 2003 at 02:38:02PM -0700, Hugh E Cruickshank wrote:
Hi Wayne:
That's good to know. I thought that it might be the case (as it is
with SAMBA), but I did not see anything obvious in the man pages
(that or I am blind - always a good possibility).
It is documented in the
Yes, the man page clearly states:
Note that you should not send the rsync server a HUP sig-
nal to force it to reread the /etc/rsyncd.conf. The file
is re-read on each client connection.
So I am obviously blind or at least not as attentive as I should be.
Hugh, I'm fairly new to rsync myself, so hopefully other
rsync gurus can either confirm or correct my thoughts here.
My comments are below.
Hugh E Cruickshank [EMAIL PROTECTED] wrote:
Hi All:
I am new to rsync so be gentle with me. I have been able to get
Me too :)
rsync working enough to
Date: Mon Jul 7 07:10:40 2003
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv20878
Modified Files:
wildtest.txt
Log Message:
A few more tests.
Revisions:
wildtest.txt1.2 = 1.3
Date: Mon Jul 7 07:22:08 2003
Author: wayned
Update of /data/cvs/rsync/lib
In directory dp.samba.org:/tmp/cvs-serv21776
Modified Files:
wildmatch.c
Log Message:
Silence some compiler warnings on HP-UX.
Revisions:
wildmatch.c 1.10 = 1.11
Date: Mon Jul 7 07:28:02 2003
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv22201
Modified Files:
wildtest.txt
Log Message:
Commented-out a test that wasn't consistent across all platforms.
Revisions:
wildtest.txt1.3 = 1.4
26 matches
Mail list logo
