Hi, I got an issue using rsync that might not be related to rsync at all. But please let me explain. I am using rsync in a script to synchronize two Volumes. So far so good this is an easy task. I set up a cron job to do it on a regular schedule. What happens is, there is a difference in the result between running the script straight form the shell or by cron. If done by cron some signs got converted. Example: Running straight on shell rsync copies these kind of files: SCHNITT/Render Files/*Vorlage Bleskin_990101_NB_n-tv/Vorlage Blesk-FIN-0000000b Running by cron, rsync exchanges the sign *: SCHNITT/Render Files/#342#200#242Vorlage Bleskin_990101_NB_n-tv/Vorlage Blesk-FIN-0000000b I got no clue at all where that comes from. Please help. -- Axel Weber ( (+49) 221 456 3918 4 (+49) 221 456 3999 CBC Cologne Broadcasting Center GmbH Email: axel.weber@cbc.de <mailto:axel.weber@rtl.de> Produktionssysteme Aachener Str. 1036 50858 Koeln/Germany www.cbc.de <http://www.cbc.de>
On Sat, Mar 21, 2009 at 07:23:58PM +0100, axel.weber@cbc.de wrote:> SCHNITT/Render Files/#342#200#242Vorlage Bleskin_990101_NB_n-tv/Vorlage Blesk-FIN-0000000bThe character sequence 0343 0200 0242 is E2 80 A2 in hex. Seems to be a common sequence for something (since those characters show up via google search), but I'm not sure what they are (and you don't mention your system's character encoding). The difference in behavior between cron and shell is most likely that the environment variable LANG is set differently, and thus rsync doesn't think that the character sequence is valid for the current language (and thus it escapes it). ..wayne..