Anope.org > General Chat

IRC Config Problem

(1/3) > >>

topdog:
hi,

If someone is willing to help I'd very much appreciate it.
I'm running UnrealIrc 2.4 with Anope Services 2.7.14.
I have 4-6 servers linked to me and my issue is that, I've forgotten what I need to set in regards to: A - getting notices about whose connecting to my 4-6 other linked leaf servers, as well as B - Who changed nicknames, and all the other notices IRC opers get.
I know it has to do with flags like C c n N or something of that nature (someone correct me if I am not right on this). Thanks.

Charles Kingsley:
Hi,

This is to do with Snomasks.

/helpop ?snomasks

***** Snomasks *****
[10:26:53]  -
[10:26:53]  Snomask stands for 'Service NOtice MASK', it (mainly) controls which
[10:26:53]  server notices you will receive.
[10:26:53]  Usage: /MODE nick +s <snomask>
[10:26:53]  Ex: /MODE blah +s +cF-j
[10:26:53]  The parameter specifies which snomasks you want (or don't want).
[10:26:53]  -
[10:26:53]  Below is a list of possible snomasks:
[10:26:53]  ==-------------------------oOo-----------------------==
[10:26:53]  c = View connects/disconnects on local server
[10:26:53]  e = View 'Eyes' server messages (OperOverride, /CHG* and /SET* usage, ..)
[10:26:53]  f = View flood alerts
[10:26:53]  F = View connects/disconnects on remote servers (except U-lines)
[10:26:53]  G = View TKL notices (Gline, GZline, Shun, etc)
[10:26:53]  j = View Junk notices (not recommended for normal use)
[10:26:53]  k = View KILL notices
[10:26:53]  n = View nick changes on local server
[10:26:53]  N = View nick changes on remote servers
[10:26:53]  o = View oper-up notices
[10:26:53]  q = View rejected nick changes due to Q:lines
[10:26:53]  s = View general notices
[10:26:53]  S = View spamfilter matches
[10:26:53]  v = View usage of /VHOST command
[10:26:53]  ==-------------------------oOo------------------------==

topdog:

--- Quote ---Originally posted by chaz
Hi,

This is to do with Snomasks.

/helpop ?snomasks

***** Snomasks *****
[10:26:53]  -
[10:26:53]  Snomask stands for 'Service NOtice MASK', it (mainly) controls which
[10:26:53]  server notices you will receive.
[10:26:53]  Usage: /MODE nick +s <snomask>
[10:26:53]  Ex: /MODE blah +s +cF-j
[10:26:53]  The parameter specifies which snomasks you want (or don't want).
[10:26:53]  -
[10:26:53]  Below is a list of possible snomasks:
[10:26:53]  ==-------------------------oOo-----------------------==
[10:26:53]  c = View connects/disconnects on local server
[10:26:53]  e = View 'Eyes' server messages (OperOverride, /CHG* and /SET* usage, ..)
[10:26:53]  f = View flood alerts
[10:26:53]  F = View connects/disconnects on remote servers (except U-lines)
[10:26:53]  G = View TKL notices (Gline, GZline, Shun, etc)
[10:26:53]  j = View Junk notices (not recommended for normal use)
[10:26:53]  k = View KILL notices
[10:26:53]  n = View nick changes on local server
[10:26:53]  N = View nick changes on remote servers
[10:26:53]  o = View oper-up notices
[10:26:53]  q = View rejected nick changes due to Q:lines
[10:26:53]  s = View general notices
[10:26:53]  S = View spamfilter matches
[10:26:53]  v = View usage of /VHOST command
[10:26:53]  ==-------------------------oOo------------------------==
--- End quote ---


Ok. In the oper block can I just do something like:
snomask xwsFfgGkcCenNvoq;
If possible, I can attach my config file and maybe someone can configure an oper block (example) with the snomasks one might need if they have linked servers yet would like to see notices for both local and linked servers.

Charles Kingsley:

--- Quote ---
snomask xwsFfgGkcCenNvoq;

--- End quote ---


Yeah, you can build up a snomask like that. I guess you should just try and play with it ... Remember you can use //mode $me +s +snomaskshere so you don't need to keep opering up.

topdog:
am able with some playing around, to see who connects and nick changes remotely and locally. However, oper-up attempts locally I can see but not remotely.
How can I fix this.

Navigation

[0] Message Index

[#] Next page