IRC Services - Support
sections: home // support // mailing lists // about // download
before you request support
Please read the following few paragraphs carefully before requesting support from either the mailing lists or from the author himself.

The most commonly asked questions, which probably includes yours, have been answered many times in the past. The answers to these questions can be found in the FAQ - which we've included, free of charge, in the distribution archive. For those of you who couldn't be bothered to read that copy, you can read it online here. This is your cue to read it... do so now!

If your question is still unanswered, please read the documentation - which you probably should have read before even installing IRC Services, but probably didn't. It too was included in the distribution archive free of charge and can be viewed online at the aforementioned URL.

If by this stage you're still in the dark, it's probably because you still haven't read the FAQ or the online documentation. If you promise you have read them, go and read them again.

 
where to request support
Once you're totally sure your question does not get answered in the documentation, you can get support by joining one of the mailing lists and asking your question there. Please follow steps 1 and 2 of submitting a bug report (see right-hand pane) when submitting your support request.
 
mailing list archives
All posts to the mailing lists are archived. You may find that your question has already been answered.
   
submitting a bug report
All support is provided on the ircservices mailing list. Please include as much of the information detailed below as possible.

  1. The version of IRC Services you're running.
    The exact version information can be found at the top of the services.log file. This file is created the first time you run IRC Services.
  2. The version of ircd you're connecting services to.
    The easiest way to get this information is to issue the following command in your IRC client:
    /quote version
  3. The list of steps required to reproduce the problem.
    In order to debug the problem, we need to know the series of events leading up to the unexpected (re)action(s).
  4. Any related logfile output.
    IRC Services can be configured to create a very verbose logfile by starting it in the following way:
    ./services -debug
  5. A GDB backtrace of the core file - if possible.
    IRC Services can be configured to create a core file if it crashes. This file allows you to use a program called GDB to determine what line of code the crash occured on. This small piece of information is probably the most valuable part of your bug report.

    The output from the following steps, executed from the same directory as your ircservices binary, is sufficient:

    1. Start gdb, making use of your core file:
      gdb <services binary> <core file>
      Example:
      gdb ircservices core
      This will produce some output and present you with the gdb command line.

    2. Execute a backtrace from the gdb command line by typing the command:
      bt
    3. Copy all the output generated since step 1 and include it in your bug report.
The more information you can provide, the quicker your problem will be solved.