On Thu, Apr 15, 2010 at 1:27 PM, Jerry wrote:
> I filed a bug report the day I submitted this post. I have not received
> any feedback or acknowledgment of the report. This may even be a python
> bug. I was thinking of asking on that forum.
>
>
http://sourceforge.net/tracker/?func=detail&aid=2898
On Thu, 15 Apr 2010 18:50:13 +0200 (CEST), Mohacsi Janos
articulated:
> On Wed, 7 Apr 2010, Jerry wrote:
>
> > Using denyhosts-2.6_3 from the ports system, I am finding the
> > following error message in the "/var/log/denyhosts" log file:
> >
> >
> > 2010-04-07 07:45:25,818 - sync: ERRO
On Thu, 15 Apr 2010 11:57:32 -0500, Adam Vande More
articulated:
> On Wed, Apr 7, 2010 at 8:45 AM, Jerry
> wrote:
>
> > This error message repeats anywhere from every hour to every three
> > or four hours. I cannot seem to decipher the pattern. Is this error
> > message something I should be wo
On Wed, Apr 7, 2010 at 8:45 AM, Jerry wrote:
>
>
> This error message repeats anywhere from every hour to every three or
> four hours. I cannot seem to decipher the pattern. Is this error message
> something I should be worried about; and if so, how do I go about
> correcting it?
>
Just a guess
Dear Jerry,
Do you use denyhosts in synchrozed mode?
http://denyhosts.sourceforge.net/faq.html#4_0
Unfortunately I cannot reproduce the problem on FreeBSD 6.x and 7.x since
I don't use synchronized mode.
Can you contact the original author of Denyhosts?
http://sourceforge.net/users/phil_schwa
Using denyhosts-2.6_3 from the ports system, I am finding the following
error message in the "/var/log/denyhosts" log file:
2010-04-07 07:45:25,818 - sync: ERROR
Traceback (most recent call last):
File "/usr/local/lib/python2.6/site-packages/DenyHosts/sync.py", line 117, in
receive
Andrea Venturoli wrote:
Anyone using this?
I've used it for a long time on a 6.x box and it worked fine.
Recently I had to deactivate it since it seems to lock away every IP
which is listed in the logs.
Running on all my Servers like a charm...
no Problems known... RELENG_7 i386 and amd64 (fed
to deactivate it since it seems to lock away every IP
which
> >is listed in the logs.
> >Any hint?
> >
> > bye & Thanks
> >av.
>
> I believe denyhost has been deprecated. I use /etc/hosts.allow which
works
> fine and combines both allow and
Sahil Tandon wrote:
Andrea Venturoli <[EMAIL PROTECTED]> wrote:
Anyone using this?
I've used it for a long time on a 6.x box and it worked fine.
Recently I had to deactivate it since it seems to lock away every IP which
is listed in the logs.
Any hint?
Give more information. Which
Andrea Venturoli <[EMAIL PROTECTED]> wrote:
> Anyone using this?
> I've used it for a long time on a 6.x box and it worked fine.
> Recently I had to deactivate it since it seems to lock away every IP which
> is listed in the logs.
> Any hint?
Give more information. Which logs? Give an example.
way every IP which
> >is listed in the logs.
> >Any hint?
> >
> > bye & Thanks
> >av.
>
> I believe denyhost has been deprecated. I use /etc/hosts.allow which works
> fine and combines both allow and deny functions in one configuration file.
&
At 04:36 PM 6/5/2008, Andrea Venturoli wrote:
Anyone using this?
I've used it for a long time on a 6.x box and it worked fine.
Recently I had to deactivate it since it seems to lock away every IP which
is listed in the logs.
Any hint?
bye & Thanks
av.
I believe denyhost
Anyone using this?
I've used it for a long time on a 6.x box and it worked fine.
Recently I had to deactivate it since it seems to lock away every IP
which is listed in the logs.
Any hint?
bye & Thanks
av.
___
freebsd-questions@freebsd.org ma
13 matches
Mail list logo
