diff options
Diffstat (limited to 'bugs/tput:_No_value_for___36__TERM_and_no_-T_specified.mdwn')
| -rw-r--r-- | bugs/tput:_No_value_for___36__TERM_and_no_-T_specified.mdwn | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/bugs/tput:_No_value_for___36__TERM_and_no_-T_specified.mdwn b/bugs/tput:_No_value_for___36__TERM_and_no_-T_specified.mdwn deleted file mode 100644 index ac0cf06..0000000 --- a/bugs/tput:_No_value_for___36__TERM_and_no_-T_specified.mdwn +++ /dev/null @@ -1,23 +0,0 @@ -I have a daily backup with obnam scheduled using a cronjob. The job succeeds without problems, however the cron daemon mails the following output to me every day: - - tput: No value for $TERM and no -T specified - -I looked for the source of this message, but neither obnam nor python know about the "-T" parameter. So I tried to wrap the job in a shell script that sets the TERM environment variable if not set like this: - - if [ -z "$TERM" ]; then - export TERM=linux - fi - -But that didn't help either. Any ideas how to fix this? - ---Christian - ---- - -tput is a shell command (see "man tput"). Obnam does not use it in any way, not even -indirectly, as far as I can see. What I suspect is happening is that when you invoke commands -from your crontab, it invokes your shell, and that runs something like `.bashrc`, and you -have something that calls tput. - -As such, unless shown otherwise, I'll assume this is not a bug in Obnam, sorry. --liw -[[done]] |