Quote:
Originally Posted by unSpawn
It's not a security issue per se. It just means that some chars encountered could not be converted to something meaningful with respect to your locale settings, and the process bails out on that. Does cron report more details in it's daily log?
|
Thank's for your answer,
The only message I got in /var/log/cron/info is :
Jun 10 04:08:00 ticerosrv2 CROND[19592]: (root) CMD ( /usr/share/msec/promisc_check.sh)
Jun 10 04:08:22 ticerosrv2 CROND[16179]: (root) MAIL (mailed 121 bytes of output but got status 0xffffffff )
Nothing else.
Perhaps you have an idea of what is the locale variable name that is used ?
I see a lot of variables containing fr_FR (my locale) :
[root@ticerosrv2 ACTIF cron]$ env | grep fr_FR
LC_PAPER=fr_FR
LC_ADDRESS=fr_FR
LC_MONETARY=fr_FR
LC_NUMERIC=fr_FR
LC_TELEPHONE=fr_FR
LC_MESSAGES=fr_FR
LC_IDENTIFICATION=fr_FR
LC_COLLATE=fr_FR
LANG=fr_FR
LC_MEASUREMENT=fr_FR
LANGUAGE=fr_FR:fr
LC_CTYPE=fr_FR
LC_TIME=fr_FR
LC_NAME=fr_FR
Perhaps I can put one of this variable to fr_FR before the cron starts ?