Coring IRCD

[temp]

As I said before, I'm not really a coder, I just try to find other stuff
that people have made and modify it to my needs.  Have any idea of a quick
way to map /owho /owhois, etc, to the operspy commands?

-----Original Message-----
From: hybrid-bounces at lists.ircd-hybrid.org
[mailto:hybrid-bounces at lists.ircd-hybrid.org] On Behalf Of temp
Sent: Saturday, February 05, 2005 10:57 AM
To: 'Rachel Llorenna'; 'General IRCD-Hybrid Discussion'
Subject: RE: Coring IRCD

Thank you, that worked, that's golden now, lol, so I'll come to you with all
my stupid questions =D

-----Original Message-----
From: hybrid-bounces at lists.ircd-hybrid.org
[mailto:hybrid-bounces at lists.ircd-hybrid.org] On Behalf Of Rachel Llorenna
Sent: Saturday, February 05, 2005 10:50 AM
To: General IRCD-Hybrid Discussion
Subject: Re: Coring IRCD

Oops! Sorry about that. The m_ignore handler causes the command to be
ignored, so you need to replace the second last m_ignore field with
m_memoserv or m_nickserv, etc. It should start working properly
afterwards.

On Sat, 5 Feb 2005 10:34:38 -0700, temp <temp at feartomorrow.com> wrote:
> That defiantly stopped the ircd from coring, it's as though the command
> isn't being executed, is that just something I'll have to deal with?
> 
> -----Original Message-----
> From: hybrid-bounces at lists.ircd-hybrid.org
> [mailto:hybrid-bounces at lists.ircd-hybrid.org] On Behalf Of Rachel Llorenna
> Sent: Saturday, February 05, 2005 10:23 AM
> To: General IRCD-Hybrid Discussion
> Subject: Re: Coring IRCD
> 
> The module, being designed for HybServ2 with old versions of
> ircd-hybrid, does not have complete message handler fields.
> 
> It is probably trying to call a NULL function since you didn't specify
> one in the msgtab, which is causing ircd to core. Try adding on two
> m_ignore entries after each function name.
> 
> {m_unregistered, m_memoserv, m_ignore, m_memoserv}
> would become
> {m_unregistered, m_memoserv, m_ignore, m_memoserv, m_ignore, m_ignore}
> 
> Since your ircd cored during execution of handle_command and only
> occurs when you're an operator (which uses the second-to-last field),
> the handler only tries to execute that function when you're an
> operator. Fixing these lines should prevent the module from causing
> ircd to dump core.
> 
> Hope this helps.
> 
> On Sat, 5 Feb 2005 10:02:33 -0700, temp <temp at feartomorrow.com> wrote:
> > Hello,
> >         I'm not really much of a coder, but I downloaded this
m_services.c
> > file to take advantage of /cs /ns /ms /os /os2 (operserv2), instead of
> > having to manually type out the command.  As a non-oper, the commands
work
> > fine, they send the messages to nickserv or chanserv with no problem.
As
> > soon as I oper up and try, the ircd.cores and I can't figure out what is
> > going on that it would work for a normal user, but not for an oper.
> >
> > If anyone could help me out with this issue, I would really appreciate
it.
> >
> > m_service.c - http://www.x-ess.org/tools/m_service.c
> > gbd information - http://www.x-ess.org/tools/gbdinfo.txt
> > ircd -
> >
>
http://voxel.dl.sourceforge.net/sourceforge/ircd-hybrid/ircd-hybrid-7.0.3.tg
> > z
> >
> > I would appreciate any help I can get.
> >
> >
> 
> --
> Regards,
> 
> Rachel Llorenna (frequency)
> 
> 


-- 
Regards,

Rachel Llorenna (frequency)