Hello Wayne,
--Am Mittwoch, 25. August 2004 9:03 Uhr -0700 schrieb Wayne Davison
[EMAIL PROTECTED]:
What would you think of a tie-break for identical names that depended on
some other attribute of the files? Such as newest file wins? That
would be quite easy to add and would be deterministic,
Hello Paul,
--Am Mittwoch, 25. August 2004 16:59 Uhr +0200 schrieb Paul Slootman
[EMAIL PROTECTED]:
Ah, so you were also lying when you said that the same file existed at
more than one source; the fileNAME is the same, but the file itself is
different.
I would prefer to say that I was mistaking
it should be RSYNC_PASSWORD, not RSYNC_PASSORD
shubhra dutt wrote:
Hi Wayne,
Sorry to disturb u again,
but now i have one more very small problem.
we need not to supply the password on command line
everytime,
when we will use rsync for transferring files from one
m/c to another,i want to fix login
The environment variable RSYNC_PASSORD and commandline parameter
--password-file= are for authenticating against an rsync server. If
you're going through ssh, you don't have an rsync question. If you can't
ssh remotehost date without a password, rsync isn't going to fake up a
tty and play
Hi,
I have setup a rsync server with a rsync running as a deamon, due to security
rules I cannot open the rsync standard port (873) in the firewall.
We have to tunnel rsync through ssh.
On the client side, which is linux kernel 2.4 I have made the following script,
but
ssh -i
On Thu 26 Aug 2004, Jean-Gabriel Duquesnoy wrote:
I have setup a rsync server with a rsync running as a deamon, due to security
rules I cannot open the rsync standard port (873) in the firewall.
We have to tunnel rsync through ssh.
On the client side, which is linux kernel 2.4 I have made
On Thu, Aug 26, 2004 at 05:14:53PM +0200, Jean-Gabriel Duquesnoy wrote:
Hi,
I have setup a rsync server with a rsync running as a deamon, due to security
rules I cannot open the rsync standard port (873) in the firewall.
We have to tunnel rsync through ssh.
On the client side, which is
Hi Dan,
thanks for your hint, i am now one step further, I get the following error now:
Received disconnect from xxx.xxx.xxx.xxx: 2: fork failed: Resource temporarily
unavailable
I suppose this is now happening on the second step of the script:
rsync -auz --password-file=rsync.pwd --delete
On Thu, Aug 26, 2004 at 05:48:42PM +0200, Jean-Gabriel Duquesnoy wrote:
Hi Dan,
thanks for your hint, i am now one step further, I get the following error now:
Received disconnect from xxx.xxx.xxx.xxx: 2: fork failed: Resource temporarily
unavailable
Have you verified that the rsync
On Wed, Aug 25, 2004 at 09:55:04PM -0700, shubhra dutt wrote:
we need not to supply the password on command line everytime,
If you are connecting via a remote shell (such as ssh) then this is
something that you need to solve using that remote shell (solve it for a
simpler command first, and then
https://bugzilla.samba.org/show_bug.cgi?id=1660
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=1670
Summary: softlink can't be excluded
Product: rsync
Version: 2.6.3
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
https://bugzilla.samba.org/show_bug.cgi?id=1660
--- Additional Comments From [EMAIL PROTECTED] 2004-08-26 20:34 ---
Wayne,
That's really great. It's definitely above and beyond the call of
duty to provide backward compatibility for undocumented/unsupported
features.
I really
13 matches
Mail list logo
