View Issue Details

IDProjectCategoryView StatusLast Update
0001244unrealircdpublic2003-11-20 19:43
ReporterExael23 Assigned Tocodemastr 
PrioritynormalSeverityfeatureReproducibilityalways
Status closedResolutionfixed 
Product Version3.2-beta17 
Summary0001244: Limit amount of /who output
DescriptionThis is not a complete failure, but it wanted to know that you think.
When doing "who *" responds creating flood. Could be restricted the maximum number of answer?
3rd party modules

Activities

syzop

2003-09-13 18:55

administrator   ~0003644

(see class::sendq for output flood triggers)
Anyway, maybe it would be nice to add some option to limit /who queries to a certain limit of lines (like on ircu at least, I guess others as well ":server 416 nick WHO :Too many lines in the output, restrict your query").

codemastr

2003-09-14 16:50

reporter   ~0003653

Hmm I thought we already had that? I know we did at one point... it must have gotten lost in one of the /who recodes.

shiny

2003-10-02 01:01

reporter   ~0003751

Could you maybe make a way to still get all the output, for those of us who have scripts to /who $chan on join. I rely on extensive output for /who to keep my internal address list up to date.

syzop

2003-10-02 03:12

administrator   ~0003752

Last edited: 2003-10-02 03:14

Yes of course /who #chan won't be affected (uh I think codemastr already thought of that at least), many scripts use it for internal address list purposes... It's more about limiting the X hundred line stuff.
[oh lol, you already said that, well.. I mean others use it a lot too :p]

edited on: 10-02-03 03:14

codemastr

2003-10-03 23:37

reporter   ~0003776

Added in .1949, it can be configured using set::who-limit

Issue History

Date Modified Username Field Change
2003-09-13 01:31 Exael23 New Issue
2003-09-13 18:55 syzop Note Added: 0003644
2003-09-13 18:56 syzop Severity minor => feature
2003-09-13 18:56 syzop Summary To try to reduce flood => Limit amount of /who output
2003-09-14 16:50 codemastr Note Added: 0003653
2003-09-29 16:53 codemastr Status new => assigned
2003-09-29 16:53 codemastr Assigned To => codemastr
2003-10-02 01:01 shiny Note Added: 0003751
2003-10-02 03:12 syzop Note Added: 0003752
2003-10-02 03:14 syzop Note Edited: 0003752
2003-10-03 23:37 codemastr Status assigned => resolved
2003-10-03 23:37 codemastr Resolution open => fixed
2003-10-03 23:37 codemastr Note Added: 0003776
2003-11-20 19:43 syzop Status resolved => closed