ntop strange message

2003-02-24 Thread UnKnown
Hi everyone, I resently install the ntop package in one box to tray it, since the first day I started to recive this info with the log check report. I think its related with the name servers or something but cant get why, how to fix it or where is the error, minerva2 is the server runing the ntop a

ntop strange message

2003-02-24 Thread UnKnown
Hi everyone, I resently install the ntop package in one box to tray it, since the first day I started to recive this info with the log check report. I think its related with the name servers or something but cant get why, how to fix it or where is the error, minerva2 is the server runing the ntop a

Re: Strange message

2001-02-22 Thread BERGAMO Jean-Louis
perldoc perllocale [...] LOCALE PROBLEMS You may encounter the following warning message at Perl startup: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = "En_US",

Re: Strange message

2001-02-22 Thread BERGAMO Jean-Louis
perldoc perllocale [...] LOCALE PROBLEMS You may encounter the following warning message at Perl startup: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = "En_US",

Strange message

2001-02-22 Thread Javier Castillo Alcibar
Title: Strange message     Hi all,     when I install or upgrade or remove a package, I always get this message: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings:     LANGUAGE = (unset),     LC_ALL = (unset),     LC_CTYPE

Strange message

2001-02-21 Thread Javier Castillo Alcibar
Title: Strange message     Hi all,     when I install or upgrade or remove a package, I always get this message: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings:     LANGUAGE = (unset),     LC_ALL = (unset),     LC_CTYPE

Re: Strange message in logs

2000-04-15 Thread Chris Wagner
At 08:04 AM 4/12/00 +0200, Tamas TEVESZ wrote: > > AFAIK, the hosts.* files only affect daemons run out of inetd, not stand-alones. >not true. they are ued by any program which has libwrap support. But is that enabled by default? Or is modification required. I did some testing a while back and n

Re: Strange message in logs

2000-04-12 Thread Tamas TEVESZ
On Tue, 11 Apr 2000, Chris Wagner wrote: > AFAIK, the hosts.* files only affect daemons run out of inetd, not > stand-alones. not true. they are ued by any program which has libwrap support. -- [-] kazmer at any cost ! ++ Minek olvasol linux-kezdot ha nem birod ? - sstu

Re: Strange message in logs

2000-04-12 Thread Chris Wagner
At 05:42 PM 4/10/00 +1000, Robert Ruzbacky wrote: >Apr 9 06:47:39 ns tcp-env[17281]: warning: /etc/hosts.allow, line 11: can't verify hostname: gethostbyname(114.trusted.net) failed >Apr 9 06:47:40 ns tcp-env[17281]: refused connect from 209.140.0.114 A lookup: can't get "114.trusted.net" host e

Re: Strange message in logs

2000-04-10 Thread Phil Pennock
Typing away merrily, Robert Ruzbacky produced the immortal words: > Apr 9 06:47:39 ns tcp-env[17281]: warning: /etc/hosts.allow, line 11: can't > verify hostname: gethostbyname(114.trusted.net) failed > Apr 9 06:47:40 ns tcp-env[17281]: refused connect from 209.140.0.114 > Apr 9 06:56:54 ns tcp

Strange message in logs

2000-04-10 Thread Robert Ruzbacky
Hi! I get the following error messages in my log: Apr 9 06:47:39 ns tcp-env[17281]: warning: /etc/hosts.allow, line 11: can't verify hostname: gethostbyname(114.trusted.net) failed Apr 9 06:47:40 ns tcp-env[17281]: refused connect from 209.140.0.114 Apr 9 06:56:54 ns tcp-env[17346]: connect f