Release Notes

 


gadfly

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

gadfly

The following copyright is modified from the python copyright.


Copyright Notice




The gadfly and kjbuckets source is copyrighted, but you can freely use and


copy it as long as you don't change or remove the copyright:


Copyright Aaron Robert Watters, 1994


                       All Rights Reserved


Permission to use, copy, modify, and distribute this software and its


documentation for any purpose and without fee is hereby granted,


provided that the above copyright notice appears in all copies and that


both that copyright notice and this permission notice appear in


supporting documentation.


AARON ROBERT WATTERS DISCLAIMS ALL WARRANTIES WITH REGARD TO


THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND


FITNESS, IN NO EVENT SHALL AARON ROBERT WATTERS BE LIABLE


FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES


WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN


ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT


OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.


Signature (obsolete)




       Aaron Robert Watters


       Department of Computer and Information Sciences


       New Jersey Institute of Technology


       University Heights


       Newark, NJ 07102


               phone (201)596-2666


fax (201)596-5777


home phone (908)545-3367


email: aaron@vienna.njit.edu

This documentation applies to the following versions of Splunk: 3.2 , 3.2.1 , 3.2.2 , 3.2.3 , 3.2.4 , 3.2.5 , 3.2.6 , 3.3 , 3.3.1 , 3.3.2 , 3.3.3 , 3.3.4 , 3.4 , 3.4.1 , 3.4.2 , 3.4.3 , 3.4.5 , 3.4.6 , 3.4.8 , 3.4.9 , 3.4.10 , 3.4.11 , 3.4.12 , 3.4.13 , 3.4.14 View the Article History for its revisions.


You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.