Hello all, I'm new so pardon this email if my questions are regular
ones...
First, is there a search for the archives?
Second, I am working on a script and would like Rsync compare all the
text files in DirectoryA and in DirectoryB/below. I then want it to copy
any of the .txt files that are not
I'm using 2.4.4-1 from the redhat RPM.
I'm rsyncing a directory tree with --backup --backup-dir= and also a number of
--exclude arguments and it dies. If I run with -vvv, it dies at this point
here:
.
.
.
make_file(-1,var/tmp)
make_file(-1,var/ucd-snmp)
make_file(-1,var/ucd-snmp/snmpd.conf)
s
On Thu, Feb 08, 2001 at 11:08:45AM -0500, Diab Jerius wrote:
...
> Ok, I wasn't considering the fact that the client may be traversing
> symbolic links to create the file list (I use the -x flag, and had
> that fixed in my mindset).
>
> As for determining if the path is within the module; df (und
On 8 Feb, Dave Dykstra wrote:
>
> The problem with full pathname symlinks and "use chroot = no" is that it
> can let somebody affect things outside of the module. For example,
> somebody could first upload a symlink to a directory outside of the module
> and then write into it. I implemented t
On Thu, Feb 08, 2001 at 10:56:15AM -0500, Diab Jerius wrote:
> On 8 Feb, [EMAIL PROTECTED] wrote:
> > It may be that you can fix your problem without modifying rsync or getting root
>access to do chroot, simply by making your symlinks relative in the source.
> > If /module/dir/link points to /o
Excellent. Basic system administration: relative links are (almost) always
preferable to absolute links... think nfs.
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Colorado TC
1880 Industrial Circle
Suite D
Longmont, CO 80501
[EMAIL PROTECTED]@[EMAIL PROTECTED] on 02/
On 8 Feb, [EMAIL PROTECTED] wrote:
> It may be that you can fix your problem without modifying rsync or getting root
>access to do chroot, simply by making your symlinks relative in the source.
> If /module/dir/link points to /othermodule/otherdir, perhaps you could point it to
>../../othermod
On Thu, Feb 08, 2001 at 09:35:17AM -0600, [EMAIL PROTECTED] wrote:
> It may be that you can fix your problem without modifying rsync or getting
> root access to do chroot, simply by making your symlinks relative in the
> source. If /module/dir/link points to /othermodule/otherdir, perhaps you
>
It may be that you can fix your problem without modifying rsync or getting root
access to do chroot, simply by making your symlinks relative in the source.
If /module/dir/link points to /othermodule/otherdir, perhaps you could point it to
../../othermodule/otherdir, for instance.
Tim Conway
[E
No. no prompt for username. you say who you are in the rsync invocation, usually in
the form of
username@rsyncdhost::module/path. Otherwise, it says you are whoever you're logged in
as (sometimes $USER, sometimes $LOGNAME. It depends on the system (I think).
Incidentally, since you're send
On Thu, Feb 08, 2001 at 01:25:22AM -, Wrieth, Henry wrote:
> in the server config file, I tried
> secrets file = /app/rsync/config/secret
> auth users = iwmaster
> where 'cat /app/rsync/config/secret'
> iwmaster:mah
>
> on the client I try:
> /app/rsync/bin/rsync /tmp/mahesh/test webtest::cSe
On Thu, Feb 08, 2001 at 08:43:27AM -0500, Diab Jerius wrote:
> Dave,
>
> Thanks, that's exactly it. I can't set chroot=yes, as I'm not running
> the server as root. As much as it's nice to have software prevent you
> from shooting yourself in the foot, when you really want to, it should
> let y
Dave,
Thanks, that's exactly it. I can't set chroot=yes, as I'm not running
the server as root. As much as it's nice to have software prevent you
from shooting yourself in the foot, when you really want to, it should
let you. Is there any way around this?
Diab
On 7 Feb, Dave Dykstra wrote
13 matches
Mail list logo
