There is some module that information about users entering a channel, exit, changes in channel-mode users, etc in debug channel? ircu type
0.
module input / output users
module input / output users
][: SaturNet - Comunidad IRC Network :][
http://www.saturnet.org/
http://www.saturnet.org/
Re: module input / output users
http://www.unrealircd.com/files/docs/un ... e_snomasks
Such information doesn't need to be sent to a channel, they can be sent to opers directly. This will save bandwidth and cpu cycles in the long run. It also removes the requirement of opers having to idle in a specific channel. Which also wastes resources.
To explain, if you send a message to a channel, unreal loops through a function to send the message to every user in the channel. if you use snomasks, unreal loops through and only sends to the opers that have the associated mode set. This makes it so not every oper sees the message but just the ones that need/want the information and is not sent needlessly to everyone. snomasks can also be automatically assigned when the /oper command is issued so the oper doesn't even need to set the modes themselves. With the invention and smart use of /*ops commands, the requirement to use a channel for oper communication was removed making it so opers can freely be anywhere without actually being anywhere ;P
Example: There are 20 opers in #Opers, only 5 need/want to see joins. Using snomasks, only 5 get the message without being in any specific channel. Using a log channel all 20 get the message whether they need/want to or not. Making 15 messages sent needlessly. This may not seem like a lot, however, when you have a busy server bandwidth and other resources become extremely valuable.
If you really want it in channel then most services/stats packages can log this stuff to a channel.
Such information doesn't need to be sent to a channel, they can be sent to opers directly. This will save bandwidth and cpu cycles in the long run. It also removes the requirement of opers having to idle in a specific channel. Which also wastes resources.
To explain, if you send a message to a channel, unreal loops through a function to send the message to every user in the channel. if you use snomasks, unreal loops through and only sends to the opers that have the associated mode set. This makes it so not every oper sees the message but just the ones that need/want the information and is not sent needlessly to everyone. snomasks can also be automatically assigned when the /oper command is issued so the oper doesn't even need to set the modes themselves. With the invention and smart use of /*ops commands, the requirement to use a channel for oper communication was removed making it so opers can freely be anywhere without actually being anywhere ;P
Example: There are 20 opers in #Opers, only 5 need/want to see joins. Using snomasks, only 5 get the message without being in any specific channel. Using a log channel all 20 get the message whether they need/want to or not. Making 15 messages sent needlessly. This may not seem like a lot, however, when you have a busy server bandwidth and other resources become extremely valuable.
If you really want it in channel then most services/stats packages can log this stuff to a channel.
Configuration - https://www.unrealircd.org/docs/Configuration
FAQ - https://www.unrealircd.org/docs/FAQ
FAQ - https://www.unrealircd.org/docs/FAQ