It guess I still haven't figured out the entire sematics of the --include
and --exclude options. From reading the man page, it seems to say that
what happens is that each file being checked is tested against each pattern
in order, and when one matches the tests end, and whether it is --include
or
On Fri, 26 Mar 2004, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 25, 2004 at 11:03:31PM -0500, Andrew Pimlott wrote:
>> The exact filename tested against include/exclude patterns is not
>> always obvious, and the documentation is somewhat ambiguous about it.
>> This bites particularly wh
On Fri, Mar 26, 2004 at 01:32:14PM -0800, Joseph Tam wrote:
> I was under the impression that "[global]" sets up the defaults, which
> all the other modules inherit, if they don't specify something else.
The global defaults are those that occur outside all module sections.
Just to be clear, I mean
On Fri, 26 Mar 2004, Wayne Davison wrote:
> On Fri, Mar 26, 2004 at 01:17:27AM -0800, Joseph Tam wrote:
> > [global]
> > transfer logging= false
> > syslog facility = uucp
>
> If you get rid of the [global] heading and just put those items at the
> start of the file, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi:
First let me say that rsync/cwrsync is amazing !
And sorry ! if I'm bothering you with this question...
I need to sync my work files from the WinXP Pro machine to our Solaris
one... so far so fine..
My problem is when I specify the path on the rsync
On Thu, Mar 25, 2004 at 11:03:31PM -0500, Andrew Pimlott wrote:
> The exact filename tested against include/exclude patterns is not
> always obvious, and the documentation is somewhat ambiguous about it.
> This bites particularly when using patterns starting with '/'.
Yes, this could certainly use
On Fri, Mar 26, 2004 at 02:30:48PM -0500, Paul Galbraith wrote:
> My impression is that when run as a server over a remote ssh
> connection, rsync is being started up as a process under the ssh user's
> account, instead of connecting to the root rsync server that I've got
> running out of inetd
Tim Conway wrote:
You have to have a "uid = 0" in the rsyncd.conf file for that module,
since only root can give away files, and also bypass all (except over NFS,
etc.) file protections.
For (insert diety's name here)'s sake, don't use "/" for a path, and don't
leave it un-chrooted, unless you'
On Fri, Mar 26, 2004 at 01:17:27AM -0800, Joseph Tam wrote:
> [global]
> transfer logging= false
> syslog facility = uucp
If you get rid of the [global] heading and just put those items at the
start of the file, it should work:
[...]
transfer logging= false
syslo
On Fri, Mar 26, 2004 at 12:09:08AM -0500, Andrew Pimlott wrote:
> When using the rsync server without chroot, the --link-dest and
> --compare-dest options are almost useless. This is because
> sanitize_paths is called on the link-dest directory, stripping out
> leading dots and slashes.
Yes, thos
On Fri, Mar 26, 2004 at 10:03:54AM -0500, Erik Jan Tromp wrote:
> $ rsync -aHPv rsync://host/module/single.file .
>
> receiving file list ...
> 1 file to consider
> Segmentation fault
Thanks for the report! I've fixed this bug in CVS as follows:
--- hlink.c 11 Feb 2004 05:03:04 -
On Fri, Mar 26, 2004 at 12:45:43AM -0500, Andrew Pimlott wrote:
> Is there any interest in reviving this patch?
The diff has been in the "patches" dir of CVS for a while now, and is
being considered for inclusion in a future release.
..wayne..
--
To unsubscribe or change options: http://lists.sa
On Thu, Mar 25, 2004 at 10:21:39PM -0500, Jim Salter wrote:
> Whether you did the progress report as "file [x] of [y]" or "megabyte
> [x] of [y]" or whatever would barely even matter;
Please try 2.6.1pre-1. From the NEWS file (taken from CVS, which was
just improved to make this entry better):
Oops :)
-- quote --
$ rsync -aHPv rsync://host/module/single.file .
receiving file list ...
1 file to consider
Segmentation fault
-- endquote --
The rsync process remains running until explicitly 'kill'ed. At which point, the
following is printed:
-- quote --
rsync error: received SIGUSR1 or
On Fri, 2004-03-26 14:38:22 +0100, Markus Marquardt <[EMAIL PROTECTED]>
wrote in message <[EMAIL PROTECTED]>:
> Now rsync sometimes generates messages like "file has vanished: ..." on
> STDOUT (_not_ STDERR) which breaks this processing.
Sounds at least surprising. Just prepare a patch to output
Hello,
i am using currently rsync-2.6.0 with option --log-format=%f to produce
a list of the transferred files. This list is then used to generate
hard-links for backup-purposes.
Now rsync sometimes generates messages like "file has vanished: ..." on
STDOUT (_not_ STDERR) which breaks this pro
I'm trying to get over an exasperating problem with rsync 2.5.7, but
I'm not making any headway. The nut of the problem is that the
rsync daemon seemingly ignores the "syslog facility" configuration
when running in standalone daemon mode, as opposed to being started
with inetd.
So, for example,
17 matches
Mail list logo
