Rsync et l'exclude - LinuxFr.org

Salut tout le monde.

Bon je poste ca dans la section débutant, parce qu'alors franchement c'est un problème tout con est je ne comprend toujours pas pourquoi ca ne veux pas fonctionner.

J'utilise rsync pour faire un backup de mon ordi portable (lucette), et j'ai un soucis avec l'exclusion de dossier.

Voilà mon script



#!/bin/sh

                                                                                

RSYNC=/usr/local/bin/rsync

SSH=/usr/bin/ssh

EXCPATH=/home/user1/rsync_backup/excluded.list

KEY=/home/user1/.ssh/georgette-lucette-rsync-key

RUSER=user2

RHOST=lucette

RPATH=/home/user2

LPATH=/home/user1/rsync_backup/yggdrasil

                                                                                

$RSYNC -avz --delete --exclude-from=$EXCPATH -e "$SSH -i $KEY" $RUSER@$RHOST:$RPATH $LPATH

Avec /home/user1/rsync_backup/excluded.list qui contient une seule ligne: le dossier à exclure à savoir /home/user2/dossier

Mon soucis est que rsync synchronise tout le dossier /home/user2 distant mais il prend aussi le dossier que j'avais exclu.

J'ai aussi essayé comme ca:
$RSYNC -avz --delete --exclude='/home/user2/dossier' -e "$SSH -i $KEY" $RUSER@$RHOST:$RPATH $LPATH

Mais tout pareil, ca foire.

Ma syntaxe pour l'exclude est elle bonne???

A l'aide.....

# re

Posté par LaBienPensanceMaTuer le 07 mai 2005 à 15:23. Évalué à 2.

Extrait de la page de man de rsync:

o if the pattern starts with a / then it is anchored to a particu-
lar spot in the hierarchy of files, otherwise it is matched
against the end of the pathname. This is similar to a leading ^
in regular expressions. Thus "/foo" would match a file called
"foo" at either the "root of the transfer" (for a global rule)
or in the merge-file's directory (for a per-directory rule). An
unqualified "foo" would match any file or directory named "foo"
anywhere in the tree because the algorithm is applied recur-
sively from the top down; it behaves as if each path component
gets a turn at being the end of the file name. Even the unan-
chored "sub/foo" would match at any point in the hierarchy where
a "foo" was found within a directory named "sub". See the sec-
tion on ANCHORING INCLUDE/EXCLUDE PATTERNS for a full discussion
of how to specify a pattern that matches at the root of the
transfer.

o if the pattern ends with a / then it will only match a direc-
tory, not a file, link, or device.

Donc en gros à ta place je mettrai /home/user2/dossier/ avec un / à la fin.

# re

Posté par LaBienPensanceMaTuer le 07 mai 2005 à 15:23. Évalué à 2.

Extrait de la page de man de rsync:

o if the pattern starts with a / then it is anchored to a particu-
lar spot in the hierarchy of files, otherwise it is matched
against the end of the pathname. This is similar to a leading ^
in regular expressions. Thus "/foo" would match a file called
"foo" at either the "root of the transfer" (for a global rule)
or in the merge-file's directory (for a per-directory rule). An
unqualified "foo" would match any file or directory named "foo"
anywhere in the tree because the algorithm is applied recur-
sively from the top down; it behaves as if each path component
gets a turn at being the end of the file name. Even the unan-
chored "sub/foo" would match at any point in the hierarchy where
a "foo" was found within a directory named "sub". See the sec-
tion on ANCHORING INCLUDE/EXCLUDE PATTERNS for a full discussion
of how to specify a pattern that matches at the root of the
transfer.

o if the pattern ends with a / then it will only match a direc-
tory, not a file, link, or device.

Donc en gros à ta place je mettrai /home/user2/dossier/ avec un / à la fin.

Suivre le flux des commentaires

Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.