Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: alias trouble  (Read 5964 times)

0 Members and 1 Guest are viewing this topic.

schutzstaffeln

  • Guest
alias trouble
« on: June 22, 2006, 12:51:35 PM »

hi people,

maybe its really simple but my trouble remains unresolved

i have a little trouble with aliases

cs instead of chanserv

i have included all aliases include "aliasesaliases.conf" etc

but my commands still dont work

i have read the faq many times to search for something that solves my problem but i still found nothing

if any1 can post how he/she solved his/her problem i would be really happy

thnx for ur patience :P
Logged

Dave Robson

  • Team
  • *
  • Offline Offline
  • Posts: 357
(No subject)
« Reply #1 on: June 22, 2006, 01:35:48 PM »

alias's are handled by the ircd, im doing to assuming your using unreal, which which case:

include aliases/anope.conf  <-- should fix it for you.
Logged

Jobe

  • Contributor
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 1023
    • Anope IRC Services
(No subject)
« Reply #2 on: June 22, 2006, 01:50:43 PM »

Also if for any reason you renamed the services Bots for example ChanServ to C (just an example) you may have to edit the anope.conf aliases file to reflect such changes.
Logged
Your IP: ()
My IRC Status:

Come along and visit http://www.anopequotes.org/

schutzstaffeln

  • Guest
(No subject)
« Reply #3 on: June 22, 2006, 08:06:00 PM »

Quote
Originally posted by Rob
alias's are handled by the ircd, im doing to assuming your using unreal, which which case:

include aliases/anope.conf  <-- should fix it for you.


actually im using unrealircd 3.2.5 and i included all files that i found in aliases dir

take a look of what i did

/*
 * You can also include other configuration files.
 * help.conf contains all the /helpop text. The badwords.*.conf
 * files contain all the badword entries for mode +G...
 * spamfilter.conf contains some good rules for current trojans.
 * You probably want to include them:
 */
include "help.conf";
include "badwords.channel.conf";
include "badwords.message.conf";
include "badwords.quit.conf";
include "spamfilter.conf";
include "aliases/aliases.conf";
include "aliases/anope.conf";
include "aliases/auspice.conf";
include "aliases/cygnus.conf";
include "aliases/epona.conf";
include "aliases/generic.conf";
include "aliases/genericstats.conf";
include "aliases/ircservices.conf";
include "aliases/operstats.conf";

Quote
Also if for any reason you renamed the services Bots for example ChanServ to C (just an example) you may have to edit the anope.conf aliases file to reflect such changes.


actually i dont know what u mean for services bots maybe but i made some changes trying to resolve my prob take a lood of what i did

unrealircd.conf changes
commented lines are changes that i remove because causes erorrs on rehash

/* Standard aliases */
alias NickServ { type services; };
alias ChanServ { type services; };
alias OperServ { type services; };
alias HelpServ { type services; };
alias StatServ { type stats; };

-----> when i did this nothing happend
alias ns { type services; };
alias cs { type services; };
alias os { type services; };
alias hs { type services; };
alias ss { type stats; };

------> when i did this i can still use /msg cs instead of /msg chanserv
alias ns {
//command "msg nickserv";
target "nickserv";
type services; };

alias cs {
//command "msg chanserv";
target "chanserv";
type services; };

alias os {
//command "msg operserv";
target "operserv";
type services; };

alias hs {
//command "msg helpserv";
target "helpserv";
type services; };

alias hos {
//command "msg hostserv";
target "helpserv";
type services; };


alias ss {
//command "msg stateserv";
target "statserv";
type stats; };

services.conf changes

# ...Name <nick> <string>  [REQUIRED except as noted below]
#     Specify the nicknames (first parameter) and "real" names (second
#     parameter) for the Services pseudoclients.  BotServ and DevNull may
#     be disabled by commenting out the appropriate lines below. Disabling
#     BotServ is recommended on large networks.

NickServName    "NickServ"  "Nickname Server"
ChanServName    "ChanServ"  "Channel Server"
MemoServName    "MemoServ"  "Memo Server"
BotServName     "BotServ"   "Bot Server"
HelpServName    "HelpServ"  "Help Server"
OperServName    "OperServ"  "Operator Server"
GlobalName      "Global"    "Global Noticer"
#DevNullName     "DevNull"   "/dev/null -- message sink"
HostServName   "HostServ"  "vHost Server"

# ...Alias <nick> <string>  [OPTIONAL]
#     Specify alternate nicknames for services. When a user will /msg
#     NickServAlias something, it will be forwarded to NickServName, and
#     NickServName will answer. This can be used to ease the migration
#     from another network, for example if your services are called
#     NickKeeper, ChanKeeper, etc ... and the other network calls them
#     NickServ, ChanServ, etc ...

#NickServAlias    "NickServ2"  "Nickname Server Forwarder"
#ChanServAlias    "ChanServ2"  "Channel Server Forwarder"
#MemoServAlias    "MemoServ2"  "Memo Server Forwarder"
#BotServAlias     "BotServ2"   "Bot Server Forwarder"
#HelpServAlias    "HelpServ2"  "Help Server Forwarder"
#OperServAlias    "OperServ2"  "Operator Server Forwarder"
#GlobalAlias      "Global2"    "Global Noticer Forwarder"
#DevNullAlias     "DevNull2"   "/dev/null -- message sink Forwarder"
#HostServAlias    "HostServ2"  "vHost Server Forwarder"

-------> actually when i did this the only difference was that on /who 0 o with chansev i see a bot called cs (as well as other bots like operserv or os nickserv or ns helpserv or hs hostserv or hos etc
 


NickServAlias    "ns"  "Nickname Server Forwarder"
ChanServAlias    "cs"  "Channel Server Forwarder"
MemoServAlias    "ms"  "Memo Server Forwarder"
BotServAlias     "bs"   "Bot Server Forwarder"
HelpServAlias    "hs"  "Help Server Forwarder"
OperServAlias    "os"  "Operator Server Forwarder"
GlobalAlias      "Global2"    "Global Noticer Forwarder"
#DevNullAlias     "DevNull2"   "/dev/null -- message sink Forwarder"
HostServAlias    "hos"  "vHost Server Forwarder"

alias "cs" "/msg chanserv"
alias "ns" "/msg nickserv"
alias "os" "/msg operserv"
alias "ms" "/msg memoserv"
alias "hs" "/msg helpserv"
alias "hos" "/msg hostserv"

at last i just wanna say that i tryed rehashing and proccessing commands in all possible combinations of aliases changes i did but still nothing happeds

may be im still missing something??

[Edited on 22-6-2006 by schutzstaffeln]
Logged

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405
(No subject)
« Reply #4 on: June 22, 2006, 09:15:32 PM »

Um, why are you including ALL of the services provider aliases, anope.conf will do just fine.
Logged

schutzstaffeln

  • Guest
(No subject)
« Reply #5 on: June 24, 2006, 07:43:07 PM »

Quote
Originally posted by chaz
Um, why are you including ALL of the services provider aliases, anope.conf will do just fine.


well it was my last try to adjust things
i know theyll do nothing to solve my prob but still i guess thats not a prob?? or not??


:P :) :P :D :R
Logged

katsklaw

  • Guest
(No subject)
« Reply #6 on: June 24, 2006, 08:21:06 PM »

1> Insure set::servicesname is set correctly.
2> take all the alias junk out of your unrealircd.conf
3> *ONLY* include aliases/anope.conf
4> rehash
Logged
Pages: [1]   Go Up