View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006128 | unreal | documentation | public | 2022-06-12 23:03 | 2022-06-13 08:21 |
| Reporter | armyn | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 6.0.3 | ||||
| Summary | 0006128: tkl.TKL_ADD and tkl.TKL_DEL on Eggdrop | ||||
| Description | Hi I've been logging logs for years like using /debug @log on mIRC, it's filed for each day. I found that the TKL_ADD and TKL_DEL were not registered. Do you know how to make it record? Because sometimes you have to look at the expiration time I have this in eggdrop.conf: logfile so * "/home/irclog/public_html/logs/status" Eggdrop v1.8.4 Cordially | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
what? :o |
|
|
Ah oops, sorry, it does log the TKL_ADD and TKL_DEL, it's just that there is no nickname in the line, only the usermask It is resolved |
|
|
i just still really dont understand. eggdrop logging? why would that be an unreal problem? also v.1.8.4 is old.. do upgrade your egg :) also i still don't understand. :D though: iam glad you figured it out. :D :) |
|
|
It's updated since tonight, I avoided updating because often it's complicated you have to spend time on it, and sometimes there are problems with "tcl.lib" something like that |
|
|
Seems solved (eggdrop). As for a little background: There's no nickname in TKL_ADD/TKL_DEL because the bans are not done on a nick name as tkl's are placed on hosts (or other criteria, but not nicks). For TKL_DEL it would be impossible to show nicks, of course, there would be no way. For TKL_ADD, a TKL can affect 1 nick, 1000 nicks, or 0, and that would only be "in that instant". You can look at client disconnect messages to see who was affected. For clients affected by a TKL after it has been placed, eg newly connecting clients affected by the ban, UnrealIRCd will not trigger any message. Such a feature has been requested once ("show rejected clients") but it would be quite noisy and kinda defeat the main idea of keeping troublemakers out without causing a mess. I don't think it's a great idea. Logging can slow things down quite a bit. And delivering such massive amount of rejected notices over IRC is a bad idea as it would clutter IRCOps screens and even cause them to be flooded off (SendQ exceeded). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-06-12 23:03 | armyn | New Issue | |
| 2022-06-12 23:11 | Lord255 | Note Added: 0022556 | |
| 2022-06-12 23:43 | armyn | Note Added: 0022557 | |
| 2022-06-12 23:48 | Lord255 | Note Added: 0022558 | |
| 2022-06-13 00:26 | armyn | Note Added: 0022559 | |
| 2022-06-13 08:20 | syzop | Assigned To | => syzop |
| 2022-06-13 08:20 | syzop | Status | new => closed |
| 2022-06-13 08:20 | syzop | Resolution | open => no change required |
| 2022-06-13 08:20 | syzop | Note Added: 0022560 | |
| 2022-06-13 08:21 | syzop | Note Edited: 0022560 |
