Hi,
first of all excuse my bad english...
you didn't let me answer you ...
Well, i've been just working with rsync also, and want to use
the --files-from option and write the same command.
And my question is: wouldn't it be the "correct" behavior to
provide just one file with the --files-from with
On Wed 29 Jun 2005, Diane Rolland wrote:
>
> Interactively, I get the following error:
> :rsync error: some files could not be transferred (code 23) at main.c(1045)
>
> In the /etc/rsyncd.log, for each of the files, I get:
> send_files failed to open /backup/exp_dbase_2005-06-2
> 8.gz: Permission
On Thu 30 Jun 2005, Judith Flo wrote:
> Well, i've been just working with rsync also, and want to use
> the --files-from option and write the same command.
> And my question is: wouldn't it be the "correct" behavior to
> provide just one file with the --files-from without writting a
> source dir?
Hi,
I was just thinking about the possibility of a flag that
provide rsync with a method that doesn't require a
source dir in the line command.
I mean, a method where the user just has to write a
file which contents all directorys that wants to rsync
(directorys without the same root), something l
Hello all.
I would more suspect the gzip behaviour that changes the file
permissioning during compression And can also let both files:
xxx AND xxx.gz after an error... I have found such unexpected files on
nfs systems.
By the way I am interested in a method where I could avoid to
send .
https://bugzilla.samba.org/show_bug.cgi?id=2831
--- Additional Comments From [EMAIL PROTECTED] 2005-06-30 10:00 ---
Created an attachment (id=1292)
--> (https://bugzilla.samba.org/attachment.cgi?id=1292&action=view)
Ignore EEXIST on second mkdir() call
--
Configure bugmail: https:
https://bugzilla.samba.org/show_bug.cgi?id=2831
--- Additional Comments From [EMAIL PROTECTED] 2005-06-30 10:12 ---
I should also mention that you can avoid the bug by simply never using a
trailing slash on a source path when using --relative (there's no difference in
behavior with or
https://bugzilla.samba.org/show_bug.cgi?id=2831
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=2781
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=2831
--- Additional Comments From [EMAIL PROTECTED] 2005-06-30 10:32 ---
I use rsnapshot as a backup tool to backup some files on a different location on
the same partition. I backup 3 folders, but the exclude-directory defined in
rsnapshot g
On Wed, Jun 29, 2005 at 10:39:57AM +0400, [EMAIL PROTECTED] wrote:
> I noticed that when the script is run, there are 2 instances of rsync
> running (using ps) on server H. Is this normal behaviour?
Yes. The receiving side forks into a separate generator and receiver
process.
..wayne..
--
To u
On Tue, Jun 28, 2005 at 02:22:22PM +0200, [EMAIL PROTECTED] wrote:
> Rsync works fine for me (the rules are reported below) except a point,
> rsync create an empty folders structure that I don'want.
The only way to get rsync to not create directory hierarchies that don't
contain *.txt files is to
On Wed, Jun 29, 2005 at 10:53:00AM +0400, [EMAIL PROTECTED] wrote:
> Now, I've just added a firewire disk to both servers and created a
> symlink to the mounted disk within the source and destination trees:
Rsync copies symlinks as symlinks unless the --copy-links option is
given, in which case al
13 matches
Mail list logo
