You can clone with
HTTPS or Subversion.
Something handy would be, being able to log all oper commands to a specific channel.
Everytime an oper uses an oper command, it should log it to a channel, lets say #opers with Who issued what command and on whom.
This could be handy of many reasons imo.
AFAIK this should already be possible via a combination of m_operlog and m_chanlog.
Disregard that, I thought that operlog logged to a SNOMASK as well as the disk. It might be a good idea if we added a SNOMASK to operlog for that. It would only be a one line change.
I agree with @SaberUK. Note: all opers will be able to see the snomask so we may want to consider limiting snomasks to oper classes, any thoughts?
Atilla in my case i wouldnt need such a restriction.
But i can think of people in different situations that would.
Is it possible to add so so that you need to have a flag/option/command in your operblock to be able to use/see that snomasks? I have no idea whats possible and whats not so just brainstorming.
i'll add a config options for 2.0 to log oper actions to a snomask (on/off)
in 2.2 however you'll be able to restrict snomasks to control who can receive the notices
Updated module: https://github.com/attilamolnar/inspircd/blob/insp20+operlog/src/modules/m_operlog.cpp
logs to snomask r for local R for remote
Tested, works great.
m_operlog Add tosnomask config option, to log all oper actions to sno…
If enabled, the commands can be logged to channels with m_chanlog and also other +s +r opers can see them
Fixes #325 reported by @SeLEct-