Gollum Debug and Development and Botmaster Opportunity Post: 65203

Sponsored Content

Contact Us UNIX Forum "Hall of Fame" - Our Developers Area Gollum Debug and Development and Botmaster Opportunity Post 65203 by Neo on Thursday 3rd of March 2005 01:02:46 PM

03-03-2005

Administrator

Gollum Debug and Development and Botmaster Opportunity

Project: Update "Program E" PHP/MySQL Application

Platform: Linux 2.4.20, Apache 1.3.39, PHP 4.3.10, MySQL 3.23.22-beta

References:

(1) �Program E� http://www.rydell.com/programe/

(2) ALICE/AIML http://www.alicebot.org/aiml.html

(3) TalkerBot 2.0.2 http://www.vbhacks.us/forum/showthr...18&page=1&pp=10

(4) UNIX.COM https://www.unix.com/chat-with-ibot-our-rss-robot-girl/

(5) vBulletin http://www.vbulletin.com

Project Summary:

The UNIX forums are a free, non commercial site for people to share information related to UNIX and Linux. We recently installed a PHP version of the ALICE chat bot in the UNIX forums. The bot is named Gollum. There are some small errors in the current version of �Program E� in the httpd log file. Here are the examples of the errors:

[error] PHP Notice: Undefined index: children in ./forums/alice/src/respond.php on line 186
[error] PHP Notice: Undefined index: attributes in ./forums/alice/src/util.php on line 471
[error] PHP Notice: Undefined index: value in ./forums/alice/src/util.php on line 47

There are a few other errors like the examples above.

We need someone to debug and fix these errors.

Potential Follow-On Development Work:

We are interested in refining the capabilities of this chat bot, based on advances in the AIML specification, perhaps creating a new development fork of �Program E� which does not seem to be actively supported at the moment.

Preferences:

We prefer you debug the configuration on your own platform and provide us files to upload on the production server.

Summary :

I estimate than an experienced PHP programmer, with the environment set up and in place, could debug and correct in a couple of hours. Our goal is long range development and this is the first opportunity to see how we may build a relationship that is good for the UNIX forums and advances the capabilities of our forum bot, Gollum.

Please post any questions to the Contact Us area (this thread) of the UNIX Forums:

https://www.unix.com/unix-forum-hall-of-fame-our-developers-area/17286-gollum-debug-development-botmaster-opportunity-post65203.html#post65203

Thank You,

Neo

Gollum_Debug.pdf (50.7 KB)

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

2 More Discussions You Might Find Interesting

1. Solaris

Job Opportunity

Diane Rafferty Read the rules....thanks. (editied by RTM - removed post info and closed thread)

2. Advertise with Us

UNIX Systems Administrator Opportunity

Optiver is a worldwide market maker and derivatives trading firm with offices strategically located in Chicago, Amsterdam and Sydney. Attracting very ambitious, talented and results-oriented individuals to become members of a highly selective trading and support group is a primary contributor to...

LEARN ABOUT DEBIAN

apache::session::lock::mysql

Apache::Session::Lock::MySQL(3pm)			User Contributed Perl Documentation			 Apache::Session::Lock::MySQL(3pm)

NAME

       Apache::Session::Lock::MySQL - Provides mutual exclusion using MySQL

SYNOPSIS

	use Apache::Session::Lock::MySQL;

	my $locker = Apache::Session::Lock::MySQL->new();

	$locker->acquire_read_lock($ref);
	$locker->acquire_write_lock($ref);
	$locker->release_read_lock($ref);
	$locker->release_write_lock($ref);
	$locker->release_all_locks($ref);

DESCRIPTION

       Apache::Session::Lock::MySQL fulfills the locking interface of Apache::Session.	Mutual exclusion is achieved through the use of MySQL's
       GET_LOCK and RELEASE_LOCK functions.  MySQL does not support the notion of read and write locks, so this module only supports exclusive
       locks.  When you request a shared read lock, it is instead promoted to an exclusive write lock.

CONFIGURATION

       The module must know how to connect to your MySQL database to acquire locks.  You must provide a datasource name, a user name, and a
       password.  These options are passed in the usual Apache::Session style, and are very similar to the options for
       Apache::Session::Store::MySQL.  Example:

	tie %hash, 'Apache::Session::MySQL', $id, {
	    LockDataSource => 'dbi:mysql:database',
	    LockUserName   => 'database_user',
	    LockPassword   => 'K00l'
	};

       Instead, you may pass in an already opened DBI handle to your database.

	tie %hash, 'Apache::Session::MySQL', $id, {
	    LockHandle => $dbh
	};

AUTHOR

       This module was written by Jeffrey William Baker <jwbaker@acm.org>.

SEE ALSO

       Apache::Session

perl v5.10.1							    2010-10-18					 Apache::Session::Lock::MySQL(3pm)