Tip of the day: Log files can use JSON logging. You can also send the JSON data to IRCOps on IRC.

The JSON is machine readable and contains lots of details about every log event.

Translations:Features/8/es

From UnrealIRCd documentation wiki
Jump to navigation Jump to search

Snomasks

Snomasks are server notice masks. It's a special type of user mode that controls which server notices you will receive. Only IRCOps can set snomasks.

It can be set by: /MODE yournick +s SNOMASK, for example: /MODE yournick +s +cF. To remove certain snomasks, use something like: /MODE yournick +s -c, or to remove all snomasks use /MODE yournick -s.

Jump to the right section below, depending on your version: UnrealIRCd 5 or UnrealIRCd 6

UnrealIRCd 6

IMPORTANT: In UnrealIRCd 6 the snomask letters are different compared to UnrealIRCd 5!!

In UnrealIRCd 6 the available snomasks are:

Snomask Description
b Server bans (KLINE, GLINE, SHUN, etc)
B Messages from the DNS blacklist module
c Local client connects
C Remote client connects (on other servers, except services/u-lines)
d Rejected DCC's due to Deny dcc blocks
D Debugging / junk (not recommended, possibly harmless things, noisy)
f flood notices (recommended)
j joins, parts and kicks
k kill notices (/KILL usage)
n Local nick changes
N Remote nick change notices
q Deny nick (QLINE) rejection notices
s Server notices: all other notices that do not fit in the other snomasks (includes very important messages, highly recommended)
S Spamfilter hits
o IRCOp overriding in channels (OperOverride)
O IRCOp changing user properties (/CHGNAME, /CHGIDENT, /CHGHOST, ..) or forcing a user to do things (/SAJOIN, /SAPART)
v VHOST usage

In UnrealIRCd 6 you can also create your own (new) snomasks via the log block.

You can control which snomasks IRCOps receive by default via set::snomask-on-oper, or in specific oper blocks via oper::snomask.

UnrealIRCd 5

In UnrealIRCd 5 the available snomasks are:

Snomask Module Description
b blacklist Messages from the DNS blacklist module
c built-in Local connects
D snomasks/dccreject Rejected DCC's due to Deny dcc blocks
F built-in Far connects (from other servers, except from U-lines like Services)
f built-in flood notices
k built-in kill notices
e built-in 'eyes' notices - a bit verbose (?)
j built-in Junk notices (noisy, possibly harmless things, mostly for debugging)
v built-in VHOST usage
G built-in GLINE and SHUN usage
n built-in Local nick changes
N built-in Remote nick change notices
q built-in Deny nick (QLINE) rejection notices
s built-in Receives server notices (includes the most important messages)
S built-in Spamfilter hits
o built-in Oper-up notices (/OPER usage)

You can control which snomasks IRCOps receive by default via set::snomask-on-oper, or in specific oper blocks via oper::snomask.