View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001304 | unreal | ircd | public | 2003-10-16 09:42 | 2003-10-17 01:01 |
| Reporter | sunriser | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta18 | ||||
| Summary | 0001304: Make +S Connections as a valid user / Seen user | ||||
| Description | As most of you already know, that I am currently developing a very unique set of IRCD services and have also developed a service called RoomServ. The sole purpose of this service is to ensure a room stays open and was hoping to use the service instead of a bot to make rooms stay open. Since services are a +S type user, they are NOT seen as a typical user. Is there anyway to rectify this so atleast a +S user is seen as a user when using +S Mode ???? | ||||
| 3rd party modules | |||||
|
|
Huh? [And the difference is?] |
|
|
Well I kinda worked out some of this anyways so /me tries this again. Ive noticed that +S connections don't have all the privileges like a normal connection would have. This means that they cant perform some of the functions that a normal user could do. like /names for example. >> :ChanServ names #codehq :TheChat.dyndns.org 366 ChanServ * :End of /NAMES list. Now there is 2 users in here currently:- >> :ChanServ who #codehq :TheChat.dyndns.org 352 ChanServ #CodeHQ me 126C4704.EF356DAC.32DC0C55.IP TheChat.dyndns.org Arkanoid Hr@ :0 - :TheChat.dyndns.org 352 ChanServ #CodeHQ RoomServ services.master.net services.master.net RoomServ H :1 In-Room Residential Services :TheChat.dyndns.org 315 ChanServ #codehq :End of /WHO list. There is other commands too that seem to do the samething or are not supported. Some of these I could understand why they aint supported but some of these I still think they would be handy to a services program. Basically, I guess what I'm trying to say here .. is there anyway either via code or in the config file to have an option to allow +S to utilise standard connection umodes? or maybe new service commands like SVSNAMES, etc. Anyways, its not a big deal nor a drama and its just something I thought I could suggest and throw your way. |
|
|
Ah ok, it's now clear to me. Well, your services server should maintain that information (channels, users, etc), the thing you are now trying to do is issueing remote commands, you should view it as: server1<->services-server<->user. A lot of commands are not ment to be (nor do they work) remotely. Remote names is not supported, and remote who shouldn't be supported either (so that's a bug, but there are others of that kind too). Clearly, no such commands (SVSNAMES etc) will be added, you need to maintain that data if you want to use it, your server receives everything it needs... This is a general ircd & services thing btw, nothing unrealircd-specific. |
