Hello, When using rsync 2.4.6 on a linux machine to copy a complete web directory (rescursively) on an other linux machine on my local network. For one file I got : skipping non-regular file www/svg_mysql/mysql.sock This file got the "s" flag set (and I suppose that is the problem). Anybody can tell me which option should I use to also in the syntax of the rsync command to copy this file too ? I've tried --devices without success. Regards jhb ps : sorry for my broked english... pps : here is the syntax of the command #rsync --stats --compress --rsh=/usr/bin/ssh --recursive --times --perms --l inks --delete /var/www 10.10.10.10::www-info-j
On 22 Apr 2002, Jean-Hugues BELPOIS <Jean-Hugues.Belpois@univ-brest.fr> wrote:> Hello, > > When using rsync 2.4.6 on a linux machine to copy a complete web directory > (rescursively) on an other linux machine on my local network. > For one file I got : skipping non-regular file www/svg_mysql/mysql.sock > This file got the "s" flag set (and I suppose that is the problem).That means it is something called a "unix domain socket". It's not a real file, but rather a portal through which other programs can talk to (in this case) mysql. In general you don't need to copy things like this because the program will recreate them when it is restarted, and they are not useful without a program listening. But --archive will do it for you anyhow.> ps : sorry for my broked english...Better than my French! :)> pps : here is the syntax of the command > > #rsync --stats --compress --rsh=/usr/bin/ssh --recursive --times --perms --l > inks --delete /var/www 10.10.10.10::www-info-jIf you're using a :: destination, then --rsh has no effect because ssh is not used. -- Martin
On 22 Apr 2002, Jean-Hugues BELPOIS <Jean-Hugues.Belpois@univ-brest.fr> wrote:> > > #rsync --stats --compress --rsh=/usr/bin/ssh --recursive --times --perms --links --delete /var/www 10.10.10.10::www-info-j > > > > If you're using a :: destination, then --rsh has no effect because ssh > > is not used. > > You mean that with :: the files are not encrypted and transfered in > clear ?That is correct. ssh (one colon) -- encrypted, suitable for insecure/public networks tcp (two colons) -- faster, unencrypted but with secure password access, uses rsyncd.conf See the manual for more details. -- Martin Remember your paying for QUALITY! -- Anonymous Windows XP troll on slashdot