Issue 70 in dircproxy: Issue on InspIRCd error message "Key already set Improper use of the PRIVMSG command"

1 view
Skip to first unread message

codesite...@google.com

unread,
Jul 22, 2009, 8:57:30 PM7/22/09
to dircpr...@googlegroups.com

Comment #1 on issue 70 by xsmurfster: Issue on InspIRCd error message "Key
already set Improper use of the PRIVMSG command"
http://code.google.com/p/dircproxy/issues/detail?id=70

This is my config file

Attachments:
dircproxyrc.txt 33.0 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

codesite...@google.com

unread,
Jul 22, 2009, 8:53:29 PM7/22/09
to dircpr...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 70 by xsmurfster: Issue on InspIRCd error message "Key already

set Improper use of the PRIVMSG command"
http://code.google.com/p/dircproxy/issues/detail?id=70

Not certain if other InspIRCd cause the same problem, at least freenode
doesn't have that issue. I
definitely don't have this issue conected directly to the network. I tried
3 different clients, same
thing.

What is the expected output? What do you see instead?
"Improper use of the PRIVMSG command" every minute or two

What version of the product are you using? On what operating system?
dircproxy 1.2.0 - (C) 2006 Francois Harvey -
http://dircproxy.securiweb.net/ - SSL

Please provide any additional information below.
NetBSD smallthug 5.99.7 NetBSD 5.99.7 (Smallthug) #1: Mon Jun 22 20:56:48
EDT 2009
mlal...@chimera.int.smurfturf.net i386

codesite...@google.com

unread,
Jul 23, 2009, 7:52:23 AM7/23/09
to dircpr...@googlegroups.com

Comment #2 on issue 70 by xsmurfster: Issue on InspIRCd error message "Key
already set Improper use of the PRIVMSG command"
http://code.google.com/p/dircproxy/issues/detail?id=70

I've traced this to the max_idle setting. I turned it back to 0 and
reloaded the configuration file... it went AWOL
and would flood me with the error. I restarted dircproxy and then it
disappeared.

Reply all
Reply to author
Forward
0 new messages