Issue #253 has been updated by Jonathan Clarke. Category set to Packaging Status changed from New to Closed Assigned to set to Jonathan Clarke Target version set to 1.2.1 % Done changed from 0 to 100
I have noticed similar problems before. I've commited your suggested fix to sample lsc.cron files. I found that this can also be fixed by setting "en_US.UTF-8" in /etc/default/locale (on Debian-based systems, at least). ---------------------------------------- Bug #253: Bad default character handling http://tools.lsc-project.org/issues/253 Author: Raphaël Ouazana Status: Closed Priority: Normal Assigned to: Jonathan Clarke Category: Packaging Target version: 1.2.1 Version: Hi, I use the cron job defined in LSC : <pre> 30 * * * * root [ -x #LSC_BIN ] && #LSC_BIN# -s all -c all > /dev/null 2>&1 </pre> While the command @#LSC_BIN# -s all -c all@ works fine when I launch it in a terminal, it fails when launched by cron. It was in fact a problem with the default terminal encoding. To make it work I had to add: <pre> 30 * * * * root [ -x #LSC_BIN ] && LANG=en_US.UTF-8 #LSC_BIN# -s all -c all > /dev/null 2>&1 </pre> But your meleage may vary, depending on your real configuration file encoding... Regards, Raphaël Ouazana. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
