control: tags -1 - patch + moreinfo
On Fri, 21 May 2010 14:58:14 +0200 Hannes von Haugwitz
wrote:
> Bob Proulx wrote:
> > But regardless of how I ran into this problem in general it doesn't
> > seem good for logcheck to place a requirement that the host's hostname
> > be registered in dns.
>
> S
Bob Proulx wrote:
But regardless of how I ran into this problem in general it doesn't
seem good for logcheck to place a requirement that the host's hostname
be registered in dns. A thin client wouldn't have this in every
configuration. It just isn't needed and therefore shouldn't be a
dependenc
Hannes von Haugwitz wrote:
> Bob Proulx wrote:
> > I believe what was intended was the following:
> Fixed in 1.3.8.
Thanks!
>> # Hostname either fully qualified or not.
>> if [ $FQDN -eq 1 ]; then
>> HOSTNAME=$(hostname --fqdn 2>/dev/null)
>>test -z "$HOSTNAME" && HOSTNAME=
tags 574858 +moreinfo
thanks
Bob Proulx wrote:
> I believe what was intended was the following:
# Hostname either fully qualified or not.
if [ $FQDN -eq 1 ]; then
HOSTNAME="$(hostname --fqdn 2>/dev/null)"
else
HOSTNAME="$(hostname --short 2>/dev/null)"
fi
Fixed i
Package: logcheck
Version: 1.3.7
Severity: normal
After installing logcheck on a system it posted an error to the cron
mail address hourly. An untrapped script error was posting stderr
output to cron. It originated here:
# Hostname either fully qualified or not.
if [ $FQDN -eq 1 ]; then
5 matches
Mail list logo
