Login or Register to Ask a Question and Join Our Community


Complex Event Processing RSS News

Coral8 Developer?s License

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Coral8 Developer?s License
# 1  
Old 12-09-2007
Coral8 Developer?s License
Tim Bass
Sun, 09 Dec 2007 05:03:08 +0000
I agree with Marc Adler regarding, Coral8 and Transparency.***
Marc discusses the the fact that Coral8 lets you download their*full development environment without any requirement to get a license key.** A Coral8 license is only needed when you move into production.* This is really great for kicking the tires and looking under the hood.
There is something I wish Coral8 would change, however.
Coral8’s development license, as I read it,*is only valid*for a single CPU machine.** However, most folks today run multiple CPUs even in their development environment, especially if they are running Linux.**If you want to*do any development on a multiple CPU machine you have to*contact Coral8.
In my opinion, it*would be good if Coral8 would open their “easy” development license up to multiple CPU Linux servers since most of us run multiple CPU Linux servers even in the development environment.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Updating the license tag in XML file with new license

Hi All, I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml. The content of files is in following format: System.xml: <?xml version="1.0"?> <!DOCTYPE Configuration SYSTEM "SystemVariables.dtd"> <usageConfiguration... (2 Replies)
Discussion started by: Pramod_T
2 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

rbot

RBOT(1) 							   rbot man page							   RBOT(1)

NAME

       rbot - IRC bot written in ruby

SYNOPSIS

       rbot [{[-d] | [--debug]} {[-h] | [--help]} {[-v] | [--version]} {[-l LEVEL] | [--loglevel LEVEL]} {[-b] | [--background]} {[-p PIDFILE] |
	    [--pidfile PIDFILE]}] [confdir]

DESCRIPTION

       rbot starts the Rbot (ruby IRC bot).

OPTIONS

       This program follow the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included
       below.

       -d, --debug
	   Display debug information (very verbose).

       -h, --help
	   Show summary of options.

       -v, --version
	   Display version information.

       -l LEVEL, --loglevel LEVEL
	   Sets the minimum log level verbosity. Possible values for the loglevel are 0 (DEBUG), 1 (INFO), 2 (WARN), 3 (ERROR), 4 (FATAL). The
	   default loglevel is 1 (INFO messages). The logfile is located at BOTDIR/BOTNAME.log and doesn't contain IRC logs (which are located at
	   BOTDIR/logs/*), but only rbot diagnostic messages.

       -b, --background
	   Background (daemonize) the bot.

       -p PIDFILE, --pidfile PIDFILE
	   Write the bot pid to PIDFILE. The default pidfile is BOTDIR/rbot.pid.

       BOTDIR
	   Path to the directory where are stored the bot's configuration files. The default config directory is ~/.rbot.

VERSION

       This manual page was written by Marc Dequenes (Duck) Duck@DuckCorp.org for the Debian(TM) system (but may be used by others). Permission is
       granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version
       published by the Free Software Foundation.

       On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.

AUTHORS

       Marc Dequenes <Duck@DuckCorp.org>
	   Debian(TM) package maintainer

       Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
	   rbot maintainer

COPYRIGHT

       Copyright (C) 2004-2009 Marc Dequenes (Duck)
       Copyright (C) 2010 Giuseppe Bilotta

rbot 0.9.15							     20100701								   RBOT(1)