Anope IRC Services
Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: Ankara on June 07, 2006, 06:52:24 AM
-
I am having a problem getting hostserv to send memos
I checked my config file:
HSRequestMemoUser
HSRequestMemoOper
are uncommented.
I didnt even notice til someone msg'd me asking
when their request would be dealt with
(other than the memo thing, the module works)
anope1.74 + Unreal 3.2.4 (debian)
other than that no other problems or indications
services has been running without a hitch since it was
released. (in fact it's been running without a hitch in various
versions for two years. :D )
thanks for any ideas.
Ankara
-
Did you restart after enabling those options?
-
Yeah, and I just did again now to make sure..
nothing.
(btw memoserv is working fine, can
send and receive all over the place)
[Edited on 8-6-2006 by Ankara]
-
Run anope in debug mode and try it then, see what its up to.
-
Interestingly enough,
I see this in debug mode:
[Jun 08 13:15:22.323497 2006] debug: [hs_request] Set config vars: MemoUser=0 MemoOper=0 MemoSetters=0 DBName='hs_request.db'
but my services.conf says this:
HSRequestMemoUser
HSRequestMemoOper
#HSRequestMemoSetters
I assume these just needed to be uncommented.
should I be setting them to =1?
-
uncommenting them should do the trick. Please insure that you have edited the correct copy of services.conf .. and not accidently edited the example.conf or the wrong copy of services.conf
-
yeah it's working perfectly *except* for the hs_request memos
and the proper config is in use
-
this is because of a little bug i think... try putting a space behind HSRequestMemoUser and HSRequestMemoOper
i have noticed this particular problem before with my own modules. if there is no space behind the variable name, and it is a PARAM_SET, it sets the variable to 0 instead of 1. i make a habbit of always putting a 1 behind them, just to make sure it ll recognise the variable.
i do not know whether this particular behavious is normal or whether it s just something that was overlooked. would have to ask a dev about that.
this is what i use in my modified version of hs_request...
# HSRequestMemoUser [OPTIONAL]
# Module: hs_request
#
# Set this if you want users to receive a memo after their vhost has been
# accepted/rejected.
#
#HSRequestMemoUser 1
# HSRequestMemoOper [OPTIONAL]
# Module: hs_request
#
# Set this if you want your ircops (opers and admins) to receive a memo
# when a new vhost is requested (not recommended on large networks).
#
#HSRequestMemoOper 1
# HSRequestMemoSetters [OPTIONAL]
# Module: hs_request
#
# Set this if you want the hostsetters to receive a memo when a new vhost
# is requested (not recommended on large networks).
#
#HSRequestMemoSetters 1
[Edited on 9-6-2006 by Viper]
-
Wow that is so odd....
Ok putting a space in there, dint do the trick,
however, putting a 1 in after each variable
made it work.
I noticed in the uncompiled module there is a config option
and they are all set to 0
Perhaps this is why.
-
those are the default values, however if it is defined in the config, it should take those, and both a 0 and a 1 will probably be seen as a 1, for some reason it just don't read it without a space or in your case also a number or so. it should though, it s only supposed to look whether they are defined or not... weird