View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002569 | unreal | ircd | public | 2005-06-21 14:49 | 2006-11-23 13:30 |
| Reporter | WolfSage | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2.3 | ||||
| Summary | 0002569: Better WHOIS functionality - Idle Times | ||||
| Description | Instead of leaving it up to a user to provide a server name when getting idle time for a user on a different server, I believe that should be handled by the IRCD itself. So, after some experimentation, I devised a simple method to do it. It appears stable, my only concern is the effects it may have on a larger networks. Included is the diff file. | ||||
| Attached Files | m_whois.patch (2,244 bytes) m_whois.patch-fixed (2,437 bytes) | ||||
| 3rd party modules | |||||
|
|
m_whois.patch-fixed resolved an issue with services clients. There is one issue yet that remains, getting the "End of /WHOIS list" to work properly. I'll experiment with that later. Sorry for the trouble. |
|
|
Im used to doing whois nick nick I dont see a reason for this yet dont see a reason not to get it, if it means more cpu and bandwith I dont see a reason to add it since most users on my network know to do nick nick to get what info they want |
|
|
Ahh, I was unaware /whois <nick> <nick> would produce the same results, instead of providing the server. |
|
|
I use that as well (well, I have a /w alias for that). But.. I don't want it to ALWAYS do a server whois, since for example when a server gets lagged (eg: in the time until it gets a netsplit) I would not receive any whois info. I don't think this feature suggestion is a good idea. |
|
|
I've got an alias also :p. But, like the report itself says, it may have issues on larger networks. @RandomNumber: I haven't looked into it, but you're probably going to use more bandwidth in a remote /whois. As for CPU, well, I'm sure we can sacrifice a few more cycles if it's doing something useful. I see the use for a network that has a too-large proportion of nublets, but not generally. |
|
|
Rejected, sorry :p |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-06-21 14:49 | WolfSage | New Issue | |
| 2005-06-21 14:49 | WolfSage | File Added: m_whois.patch | |
| 2005-06-21 15:41 | WolfSage | File Added: m_whois.patch-fixed | |
| 2005-06-21 15:43 | WolfSage | Note Added: 0010102 | |
| 2005-06-25 07:31 | RandomNumber | Note Added: 0010121 | |
| 2005-06-25 15:32 | WolfSage | Note Added: 0010122 | |
| 2005-06-25 17:34 | syzop | Note Added: 0010124 | |
| 2005-06-30 03:14 | w00t | Note Added: 0010148 | |
| 2006-11-23 13:30 | syzop | Status | new => closed |
| 2006-11-23 13:30 | syzop | Note Added: 0012705 | |
| 2006-11-23 13:30 | syzop | Resolution | open => no change required |
