View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001951 | unreal | ircd | public | 2004-07-12 06:22 | 2004-07-12 15:44 |
| Reporter | medice | Assigned To | |||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0001951: still some miscounting on /stats P (like 0001691) | ||||
| Description | original bug report @ http://bugs.unrealircd.org/bug_view_advanced_page.php?bug_id=0001691 this morning i played around a bit, and stats P shows wrong numbers again (additional info...) - same after a fresh restart - seemingly one client is created at startup-time... since there is "one nonexisting connection" on this port, it can't be disabled by modiefied conf-rehashing... | ||||
| Additional Information | Version: 3.2.1 - compiled as FhinXeOoZE (linux 2.4.26-grsec *** Listener on no.interest:6670, clients 1. is PERM clientsonly SSL *** Listener on no.interest:6669, clients 0. is PERM clientsonly *** Listener on no.interest:6668, clients 0. is PERM clientsonly *** Listener on no.interest:6667, clients 1. is PERM clientsonly *** Listener on no.interest:6666, clients 0. is PERM clientsonly *** Listener on no.interest:6665, clients 0. is PERM clientsonly *** Listener on no.interest:8068, clients 0. is PERM serversonly SSL *** Listener on no.interest:8067, clients 0. is PERM serversonly *** Listener on 127.0.0.1:8067, clients 0. is PERM serversonly There are 0 users and 1 invisible on 1 servers 1 operator(s) online I have 1 clients and 0 servers Current Local Users: 1 Max: 1 Current Global Users: 1 Max: 1 I was the only user - connecting via 6667 (if connection on ssl there where 2 connetions listed... | ||||
| 3rd party modules | |||||
|
|
This is not a bug.. that said syzop to me, because I already reported that :P The last bounded Port has always "1" client, even though there isn't anyone on that port. bearbeitet am: 2004-07-12 07:51 |
|
|
Yeah, the best way to think of it is like this. Back in 3.1, you had an M:line. In the M:line you specified a port. You could not change that port without a /restart. In 3.2, we simply take the last port in the list and treat it like the one from the M:line, hence it can not be deleted either. |
|
|
@codemaster sounds reasonable - is this the last port in the conf-file (so i may choose my port ;) or is this the highest port available? if second: is there a chance to config the "default port" in some way? some kind of "default;" just like ssl; an so on? |
|
|
It's the last one in the config file. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-07-12 06:22 | medice | New Issue | |
| 2004-07-12 07:50 | Rocko | Note Added: 0007001 | |
| 2004-07-12 07:51 | Rocko | Note Edited: 0007001 | |
| 2004-07-12 12:26 |
|
Note Added: 0007003 | |
| 2004-07-12 13:01 | medice | Note Added: 0007007 | |
| 2004-07-12 13:09 |
|
Note Added: 0007009 | |
| 2004-07-12 15:44 |
|
Status | new => closed |
