On 26 Apr 2002, Dave Dykstra <[EMAIL PROTECTED]> wrote:
> > Also, I would be happy to provide builds of rsync for AIX4.1.5 and
> > 4.3.3.
>
> Martin, you could probably easily give volunteers write access to selected
> binaries directories by making a password-protected module in
> /etc/rsyncd.c
On Wed, Apr 10, 2002 at 01:46:44AM -0400, Corey Stup wrote:
> Took a while to figure this one out:
>
> Since "use chroot" defaults to true, I was having issues of UID/GID's
> not mapping between servers. On AIX, if chroot() is called, the
> getpwuid() calls fail, no longer being able to find /e
Dave,
Excludes worked fine from client to server. Both systems are RedHat Linux 7.2
(2.4.18 kernel)
Rsync output on both systems (snipped):
rsync version 2.5.5 protocol version 26
Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
IPv6, 64-bit system inums, 64-bit
No, the -vv has to be on the client side. The fact that most of your
patterns don't have a '/' in them makes them pretty simply and it seems
like they ought to work. Excludes specified on the server can be overridden
by the client, however. What is the command line on the client? Do the
files
Is there a way to do debuging on the sever end? I've tried: rsync -vv --daemon
--no-detach but I dont get any output.
The exclude contains to following (I'm sure this could be done differently):
#
# Common junk directories
#
/COOKIES
/Cookies
/cookies
/TEMPOR*
/Temporary*
#
# NTUSER.DAT does NO
On Thu, Apr 04, 2002 at 02:05:56PM +0200, Lapo Luchini wrote:
> Is there any plan to do it?
> Is it maybe already in and just not documented?
It's not currently there, and there's no plan to do it. I expect a clean
patch to implement it would be accepted.
- Dave Dykstra
--
To unsubscribe or
I know this is late but nobody else appears to have responded.
On Wed, Apr 03, 2002 at 11:43:48PM -0500, Scott Lipcon wrote:
> Hello,
>
> I'm having a problem doing a remote rsync over ssh - i'm using a script that
> has worked for quite a while, using rsync 2.4.6 on both ends. I upgraded the
Max Bowsher [[EMAIL PROTECTED]] writes:
> I though that shutdown acts as below:
(no data loss)
> SUSv2 is annoyingly somewhat vague on the specifics.
So are the FreeBSD/Linux man pages. They don't specifically indicate
truncation or flushing of data, although I don't recall ever thinking
of shu
On Fri, Apr 26, 2002 at 05:40:07PM +0100, Max Bowsher wrote:
> Action of the function depends on the value of howto -
> SHUT_RD - read half of the connection is closed. The data currently in the
> socket receive buffer is discarded.
> SHUT_WR - write half of the connection is closed. The data in t
What's in rsyncd.excludes, and what's the command line. A common problem
is that people don't know exactly which path components to include in
the exclude list. Using -vv often helps with debugging excludes.
- Dave Dykstra
On Fri, Apr 26, 2002 at 11:26:38AM -0400, Paul Slinski wrote:
> I am a
On Fri, Apr 26, 2002 at 09:55:12AM +0200, Stefan Nehlsen wrote:
> On Thu, Apr 25, 2002 at 04:47:36PM -0500, Dave Dykstra wrote:
> > On Mon, Apr 01, 2002 at 06:14:38PM +0200, Michael Zimmermann wrote:
> > > 1.) Setting owner and/or group of backup files.
> > >
> > > In our servers I'm using rsync
I though that shutdown acts as below:
--
Syntax:
int shutdown(int sockfd, int howto);
returns 0 if OK, -1 on error.
Action of the function depends on the value of howto -
SHUT_RD - read half of the connection is closed. The data currently in the
socket receive buffer is discarded.
SHUT_WR - w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At Friday 26 April 2002 16:02 Dave Dykstra wrote:
> Why go through the trouble to nullify the --suffix option when --backup-dir
> is specified? I think it would be better to allow them to come in either
> order anyway.
The -suffix is initialized to
I am attempting to utilize the exclude from option in my rsync configuration
file (rather than maintain lists on users machines) but it does not appear to
be working.
One example, I placed *.mp3 in the file to keep them from syncing mp3 files to
the server and jamming up space. But rsync just
Why go through the trouble to nullify the --suffix option when --backup-dir
is specified? I think it would be better to allow them to come in either
order anyway.
- Dave Dykstra
On Fri, Apr 26, 2002 at 01:52:24AM +0200, Michael Zimmermann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
On Fri, Apr 26, 2002 at 03:11:59AM +0200, Rolf Grossmann wrote:
> Hi Dave,
>
> on Thu, 25 Apr 2002 15:52:56 -0500 Dave Dykstra wrote
> concerning "Re: 4.4BSD chflags support for rsync" something like this:
>
> > I think the --flags patch is probably fine, except that that the short
> > descript
I have a server (A) with a directory structure I want to copy to another
server (/usr/local/bin...)
On the client (B), only /usr exists (/usr/local doesn't).
I used:
/opt/PKGrsync/bin/rsync -a --delete --force
--rsync-path=/opt/PKGrsync/bin/rsync --exclude=save -v -v /usr/local/bin
B:/usr/loca
On Thu, Apr 25, 2002 at 04:47:36PM -0500, Dave Dykstra wrote:
> On Mon, Apr 01, 2002 at 06:14:38PM +0200, Michael Zimmermann wrote:
> > 1.) Setting owner and/or group of backup files.
> >
> > In our servers I'm using rsync to backup to a hot standby machine.
> > The users have access to this back
18 matches
Mail list logo
