supybot-botchk(1) [debian man page]

SUPYBOT-BOTCHK(1)					      General Commands Manual						 SUPYBOT-BOTCHK(1)

NAME

       supybot-botchk - A script to start Supybot if it's not already running.

SYNOPSIS

       supybot-botchk [options]

DESCRIPTION

       supybot-botchk  is  a  script  that  will start Supybot if it detects that one is not currently running.  This can be useful for scheduling
       supybot(1) to run via cron(8).

OPTIONS

       -h, --help
	      Show summary of options.

       -v, --verbose
	      Use verbose output when running the script.

       --botdir=BOTDIR
	      Determines which directory the bot be started in.

       --pidfile=PIDFILE
	      Specifies the name of the pidfile to look for.  This should be relative to the given botdir.

       --supybot=SUPYBOT
	      Specifies the location of supybot(1).  If this is not given, it is assumed that supybot(1) is in the user's $PATH.

       --conffile=CONFFILE
	      Specifies the path to the bot's configuration file.  This will be used when (re)starting the bot.

SEE ALSO

       python(1), supybot(1), supybot-test(1), supybot-wizard(1), supybot-adduser(1), supybot-plugin-doc(1), supybot-plugin-create(1)

AUTHOR

       This manual page was originally written by James Vega <jamessan at supybot dot com>.  Permission is granted to copy, distribute and/or mod-
       ify this document under the terms of the Supybot license, a BSD-style license.

								    APRIL 2005							 SUPYBOT-BOTCHK(1)

IBID-PLUGIN(1)						     Ibid - Multi-protocol Bot						    IBID-PLUGIN(1)

NAME

       ibid-plugin - Plugin testing developer environment for Ibid

SYNOPSIS

       ibid-plugin [options...]  [plugin[-]|plugin.Processor[-]...]

DESCRIPTION

       This utility is for testing Ibid plugins without the full bot environment.  This means testing can be performed offline and without loading
       all the available plugins.

       This should be run in a configured Ibid bot directory.

       All the listed plugins and Processors will be loaded on start-up.  Naming a plugin loads the complete plugin.  Suffixing a - to	the  name,
       ignores that plugin or Processor instead of loading it.

OPTIONS

       -c, --configured
	      Load all configured plugins, instead of only the core and requested plugins.

       -o, --only
	      Don't  load  the	Ibid core plugins, only the plugins requested.	Note that without the core plugin to pre- and post-process events,
	      most other plugins won't function correctly.

       -p, --public
	      By default, ibid-plugin emulates a private conversation with the bot.  With this option, the conversation is considered to be public
	      and the bot will have to be addressed to provoke a response.

       -v, --verbose
	      Increase verbosity.  The final form of each Event object will be displayed before any responses.

       -h, --help
	      Show a help message and exit.

FILES

       ibid.ini
	      Locates the database to act upon by looking for the [databases].ibid value in the bot configuration file in the current directory.

BUGS

       ibid-plugin doesn't emulate a complete Ibid environment, and will ignore all of the following:

       *      Delayed and periodically executed functions.

       *      Messages to alternate sources.

       *      Messages directly dispatched, rather than added to responses.

       *      Permissions.  All permissions are granted to the user.

SEE ALSO

       ibid(1), ibid.ini(5), ibid-setup(1), http://ibid.omnia.za.net/

Ibid 0.1							    March 2010							    IBID-PLUGIN(1)