On 21 Feb 2001, AFRIZAL-IPTN <[EMAIL PROTECTED]> wrote:
> I have tried some times to unscribe from milling list but until now I
> still fail to unscribe. I hope some one tell me how to unscribe from list
> samba.
Go to this page:
http://lists.samba.org/mailman/listinfo/rsync
type in your e
I have tried some times to unscribe from milling list but until now I
still fail to unscribe. I hope some one tell me how to unscribe from list
samba.
Perhaps this is already discussed by the IPv6 proposed patches. I
personally haven't looked at them in detail yet, but it seems like it
would be nice to merge in support.
The major problem is that IPv6 literal addresses include '.' and ':'
as delimiters, which conflicts with the historical usage
They're in roots path when you're logged in. Remote command execution is subtly
different from remote login.
I suspect that if you ssh some.machine.com rsync --help, you'll find that rsync isn't
found from a non-interactive shell. Commonly, remote command execution acts as a
login shell if in
On Tue, Feb 20, 2001 at 05:05:53PM -0500, Forrest Aldrich wrote:
> rsync -avz -e ssh some.machine.com:/usr/local/apache/ /local5/machine
> sh: rsync: not found
Try adding --rsync-path=/path/to/rsync to your rsync invocation.
--
Jos Backus _/ _/_/_/"Modularity is not a h
You're fine. As long as port 22 is open, you're good to go. All traffic will be
encapsulated inside the ssh connection, which is from some non-privileged port on the
calling machine and port 22 on the server with sshd.
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Colorado
But I'm getting this error:
rsync -avz -e ssh some.machine.com:/usr/local/apache/ /local5/machine
sh: rsync: not found
unexpected EOF in read_timeout
Same happens on another machine, which is running packet filters.
But the odd thing is that rsync and ssh are all in root's $PATH, as
evidenced
I'm having a problem with rsync while running on a machine that uses packet
filters (FreeBSD)... I presume this is because I need to permit out/in the
primary port that rsync uses -- but I'm not sure if it routes all traffic
through that port number or if it then uses unprivileged ports after
Hi,
I've seen others with this problem, and
thought I'd see if anyone had yet found a solution. It occurs for me on Solaris8
SPARC, and seems to be exclusive to solaris8 in my reading of the archive. Has
anyone succesfully run this on Solaris8?
I myself have succesfully managed to
transf
On Sun, Feb 18, 2001 at 03:28:20AM +0100, Assar Westerlund wrote:
> This might be caused by the rsync server making a chroot() to
> /var/ftp-mirror, thus failing to follow the symbolic links into
> home/ftp. No chroot occurs when using ssh a transport. So you can
> try adding 'use chroot = no' o
10 matches
Mail list logo
