Upon invocation from cron, backup-manager has some HAL_... environment variables containing much data.
From /usr/share/backup-manager/sanitize.sh, around line 97:
function replace_deprecated_booleans()
{
for line in $(env)
do
key=$(echo "$line" | awk -F '=' '{print $1}') value=$(echo "$line" | awk -F '=' '{print $2}')
#...parse, warn and modify...
done
Now set some environment variable inside bash to some very long value and check the export of "env": The value is not quoted, but broken in several lines. This breaks the above construct.
Better would be to use "export -p" or to just loop through known BM_... variables.
Upon invocation from cron, backup-manager has some HAL_... environment variables containing much data.
From /usr/share/ backup- manager/ sanitize. sh, around line 97:
function replace_ deprecated_ booleans( )
{
for line in $(env)
value= $(echo "$line" | awk -F '=' '{print $2}')
do
key=$(echo "$line" | awk -F '=' '{print $1}')
#...parse, warn and modify...
done
Now set some environment variable inside bash to some very long value and check the export of "env": The value is not quoted, but broken in several lines. This breaks the above construct.
Better would be to use "export -p" or to just loop through known BM_... variables.