Package: lsb-base
Version: 3.2-4
Severity: minor
File: /lib/lsb/init-functions
Gentlemen, I notice the possibility of raw terminal escapes ending up
in email messages.
That this can never be right is shown by the fact that one does not
know what kind of terminal the person reading the email will be using.
This is not to say you should go further and begin sending HTML mail,
but instead take a step back: do further tests to determine if you are
really dealing with a terminal.
For instance, we see that you do
if [ "x$TERM" != "xdumb" ]
but how about
$ test $TERM
or
if [ "x$TERM" != "" ]
in the first place!
Another test is
$ test -t
Only after being very sure that you are dealing with a real terminal
should you proceed to send tput(1) stuff.
>>>>> "m" == moblock <[EMAIL PROTECTED]> writes:
>> 2. What's with the raw terminfo escapes !!! Yuck. Took out for this
>> email via col -b.
>>
>> >>>>> "A" == Anacron <[EMAIL PROTECTED]> writes:
>>
A> /etc/cron.daily/logrotate:
A> cat: /var/run/moblock.pid: No such file or directory
A> kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or
kill -l [sigspec]
A> error: error running postrotate script for /var/log/moblock.log
A> run-parts: /etc/cron.daily/logrotate exited with return code 1
A> /etc/cron.daily/moblock:
A> 33m*39;49m MoBlock is configured not to update the blocklists automatically.
A> 33m*39;49m To change this edit the MOBLOCK_CRON entry in
/etc/moblock/moblock.conf.
m> If I understand you correctly you're talking about these:
m> 33m*39;49m
m> They result from "log_warning_msg" in /lib/lsb/init-functions (Debian
m> package lsb-base). I assume I didn't implement it wrong, so you'd have
m> to talk to that package maintainer.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
