Wayne,
Thanks for addressing the concerns. I have some comments:
On Wed, 2007-11-28 at 15:33 -0800, Wayne Davison wrote:
> The main purpose for the generated files being in CVS and/or git
> (including the magic "configure" script) is to make the build farm work.
> When a human checks out the fil
On Sat, Nov 17, 2007 at 03:48:10PM -0500, Matt McCutchen wrote:
> 1. It looks like you retroactively removed all generated files from
> the history. This may inconvenience a user who seeks to an older
> version of the source code and lacks the magic "configure" to help
> regenerate the files.
The
On Wed, Nov 28, 2007 at 01:03:48PM +0100, Paul Slootman wrote:
> configure.in is 14 seconds younger than configure.sh, and 13 seconds
> younger than config.h.in. Was it touched somehow?
Yeah, that was a mistake in the new release script that works with git.
Thanks for the note -- I've made some c
Hi,
I'm syincing i.e. /var/lib/mysql with no problems at all on 2.6.9 and
now in 3.0.0pre5, with no password between trusted hosts.
Try this nice tutorial for paswordless ssh/rsync to deeply understand
this issue, it's listed on "documentation" on the official rsync website:
http://troy.jd
Hello!
I am having following issue: when the home directory of a new user is not in
/home, but in any other directory in the root, say /copies/user, then I can
not avoit the password prompt.
I already generated the keys, uploaded to /copies/user/.ssh/authorized_keys,
checked permnissions, etc. (I d
All,
I'm experiencing a problem where rsync crashes consistently when syncing a
large file (~760MB). I am rsyncing from my windows box to my linux server.
Both ends are running the latest stable version 2.6.9 protocol version 29.
The Linux server is a 64-bit version and the windows client support
On Wednesday 28 November 2007 02:41:30 am Fabian Cenedese wrote:
> At 16:33 27.11.2007 -0500, Joe Demeny wrote:
> >I am trying to rsync a machine running CYGWIN_NT-5.2 server
> > 1.5.24(0.156/4/2) to another which runs FreeBSD 6.2-STABLE; both with
> > rsync 2.6.9.
> >
> >I'm trying to "pull" the f
On Wed, 2007-11-28 at 02:29 -0800, Johan Huysmans wrote:
> I noticed it is working with the rysnc-3.0.0-pre5, or at least the protocol
> of it. Is it possible to use that protocol for the curren stable release.
No, the protocol is new in rsync-3.0.0* .
Matt
--
To unsubscribe or change options:
selinux is enabled. I changed enforcing to permissive mode and it
works now. i think i should check to see if it is necessary to run it
on my system and no matter what I learn - just disable it. thank you
guys for your help.
--
To unsubscribe or change options: https://lists.samba.org/mailman/list
> I think a very important part of using that script was to determine the
> ids, as in: what got written to /tmp/rsync.ids
> (Aside: I would have used "id > /tmp/rsync.ids", not rely on UID being
> set, I believe that's a bash extension, although I may be confused due
> to having been brought up on
On Tue, 2007-11-27 at 17:54 -0500, [EMAIL PROTECTED] wrote:
> I am not aware of SE linux running on this system unless centos is
> enabling this by default. How do I check? (I know I should not ask...)
I know I should not answer, but run "selinuxenabled; echo $?". Zero
means enabled, one means di
On Wed 28 Nov 2007, Wayne Davison wrote:
> I've just released rsync 3.0.0pre6, the latest pre-release version of
> the upcoming 3.0.0 release.
When I do:
./configure
make
I get the following:
$ make
autoconf -o configure.sh
autoheader && touch config.h.in
Configure files changed -- perhaps run
I've just released rsync 3.0.0pre6, the latest pre-release version of
the upcoming 3.0.0 release.
Things are still progressing in our efforts to stamp out bugs for the
final release. There are still some things reported earlier that I have
either not yet had a chance to fix or have been unable to
I noticed it is working with the rysnc-3.0.0-pre5, or at least the protocol
of it. Is it possible to use that protocol for the curren stable release.
Greetings Johan
Johan Huysmans wrote:
>
> whoops forgot to mention the error i receive ;)
>
> This message appears on the client side:
> rsync
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>> Hmm. Bizarre things happening when root and different behaviour when run
>> as a daemon versus from the command line. Those are the sort of symptoms
>> one gets from SELinux denials. Is SELinux enabled on this system?
>
>
>I am not aware of SE l
On Tue 27 Nov 2007, [EMAIL PROTECTED] wrote:
> On Nov 26, 2007 11:38 PM, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> > root. Set a shell script like the following as the "server" in the
> > xinetd configuration to verify that the daemon is running as root and to
> > strace it to get more informat
16 matches
Mail list logo
