* jonathan <[EMAIL PROTECTED]> [2008-02-15 02:31-0500]: > In various part of backupninja english locale is assumed. If backupninja > is run from an interactive shell, in order to test its configuration for > example, it may not be the case and some weird log lines (localised > month abbreviations) could be writen and break log parsers.
I am trying to understand better what you are saying here. If I understand correctly, what you are saying is that due to the english locale assumptions within backupninja, if a user who does not use the english locales runs backupninja in an interactive shell then the non-english locale is used which breaks ...? You say log parsers here, but I dont quite understand what that means. Do you mean to say that some of the log parsing code within backupninja fails to run properly, so they fail to match log entries that otherwise would be in english? If this is the case, can you provide an example? > It seems that isnow() function assume english locale too for day name > checking. Yeah, it does. > LANG=C could be set at the begining of the script to fix this problem. You mean at the beginning of the backupninja script itself? I suppose another solution would be to provide full localized strings for backupninja, which could be a difficult undertaking, especially since I have no clue about these things. I welcome any suggestions, and encourage patches! :) Micah
signature.asc
Description: Digital signature
