Softpanorama

May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

ovocomposer -- HPOM Correlation Composer

News HP Operations Manager Recommended Links Reference HPOM Documentation Event Correlation Event Correlation Technologies
ECS Designer            

Correlation Composer is  included with the standard HPOM 9 distribution (you do not need to order it separately).  The Composer is a front-end interface to a "super circuit", which is to say that it is a single ECS circuit that can be used to create a family wide range of correlation rules. In essence the Composer is fancy interface to ECS fact stores. The composer provides a few examples

ovocomposer is a utility for using the HP Correlation Composer with HPOM for UNIX. With this tool you can start the Correlation Composer GUI and install Correlator stores on the management server or on managed nodes.

To start use

ovocomposer -ui

The critical challenge for network and system operators today is dealing with the massive amount of information related to network, system and application problems. This information comes in many forms and the key is for your management solution to accurately understand what is important to present to your operators, what can be discarded, and what is needed for use by specialists who may need to follow a “bread-crumb trail” when diagnosing very complex problems.

Install Correlator stores on the HPOM management server system:

ovocomposer -install [ -fs fstore1 [ -fs fstore2 ... ] ] -ms

Install a Correlator store on specified HPOM agent systems:

ovocomposer -install [ -fs fstore1 [ -fs fstore2 ... ] ] -agt node1 [ node2 ... ]

Display usage: 

ovocomposer

Options
-ui
Starts the Correlation Composer UI. ovocomposer sets the event type to OpC and starts the UI in Developer’s mode.

-agt node ...
Hostnames of managed nodes where -install shall be applied.

-ms
Installs Correlator stores on the management server.

-install
Installs a Correlator store. If -fs fstore is not omitted, ovocomposer presents a numbered list of Correlator stores from the directory: /etc/opt/OV/share/conf/OpC/mgmt_sv/CO/ Select one or more Correlator stores to be installed.

-fs fstore
Specifies Correlator stores (ECS fact stores), to be installed.

Examples

Install a Correlator store on the HPOM management server system inter†actively:

# ovocomposer -install -ms
List of Correlator stores in /etc/opt/OV/share/conf/OpC/mgmt_sv/CO/: 0) empty.fs
1) demo.fs
2) my_corr.fs
Enter numbers (comma separated) to select stores:2 #

Install selected Correlator stores on agents:

# ovocomposer -install -fs test1.fs -fs test2.fs -agt sys1.my.com sys2.my.com

The Correlation Composer (herein after referred to as Composer) is a graphical user interface used to tune the prepackaged Correlators. Correlators are created using the Composer and uniquely identify a unit of logic to be applied to an event or set of events. Correlators can be used out of the box or can be easily fine tuned to fit your environment like a glove without requiring programming skills.

The Composer comes prepackaged with six Correlator Templates :

  1. event suppression,
  2. transient states,
  3. duplicate events,
  4. event timing,
  5. event create
  6. event annotation

which ease the creation of correlation solutions by providing correlation models for the most common correlation tasks.

  1. To create ECS Composer template on Mgt Server (already done on hbrpsums01d6)
    1. Requires: /var/opt/OV/share/tmp/OpC_appl/comp
    2. Upload template: opccfgupld comp
    3. Fact store must exist: /var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.fs (copy from other server)
    4. Assign Composer Circuit to Mgt Server: Actions->Server->AssignTemplate
    5. Run circuit on Mgt Server: Actions->Server->Install/Update Templates (starts opcecm)
  2. To create or edit Correlation store
    1. Make sure you are running the Hummingbird Window Manager

1. Start-> Programs-> Hummingbird Connectivity 7.0-> Exceed -> Tools -> HWM

    1. Open ecs composer in developer mode: /opt/OV/bin/ovcomposer –m d
    2. Save Correlation store in /etc/opt/OV/share/conf/ecs/CIB/OpC
    3. New Correlation store will be saved with a .fs extension (fact store)
    4. Edit NameSpace.conf in that directory to add new Correlation Store
  1. To deploy Correlation store
    1. Deploy in ovcomposer –m o does not work, use command line
    2. /opt/OV/bin/csdeploy.ovpl -p /etc/opt/OV/share/conf/ecs/CIB/OpC/deploy.conf
  2. Activate Correlation store (not sure if deploy does this or not)
    1. Run: /opt/OV/bin/ecsmgr –i 11 –update \

ecs_comp /var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.fs

    1. Check: /opt/OV/bin/ecsmgr –i 11 –info or /opt/OV/bin/ecsmgr –i 11 –fact_dump
  1. IMPORTANT UPDATE (when things get screwed up)
    1. If you are unable to load a factstore execute the following:

1. /opt/OV/bin/ecsmgr -i 11 -disable ecs_comp

2. /opt/OV/bin/ecsmgr -i 11 -circuit_reload ecs_comp \ /var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.eco 0 ecs_comp

3. /opt/OV/bin/ecsmgr -i 11 -enable ecs_comp

4. /opt/OV/bin/ecsmgr -i 11 -update ecs_comp \ /var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.fs

  1. ANOTHER IMPORTANT UPDATE (severity number changes)
    1. 4 Unknown
    2. 8 Normal
    3. 16 Warning
    4. 32 Critical
    5. 64 Minor
    6. 128 Major
  2. FYI
    1. From the ecsmgr man page:

-instance <instance>

Identifies a particular engine instance when there

are multiple instances on a host system.

The default for this option is -instance 1.

pmd: The pmd-linked correlation engine is

always instance 1.

HPOM : The HPOM Server -linked correlation

engine is always instance 11.

The HPOM Agent -linked correlation engine

is always instance 12.

  1. To Create & activate Correlation store on Agent
    1. Assign & Deploy ECS Composer template to agent
    2. Edit: ENGING_INSTANCE=12 in /etc/opt/OV/share/conf/ecs/CIB/OpC/deploy.conf
    3. /opt/OV/bin/ecsmgr –i 12 –fact_update ecs_comp /var/opt/OV/conf/OpC/ecs_comp.fs

Integration with operations

Operations offers event correlation on the management server and on supported managed nodes, uniquely allowing event correlation to be distributed among systems, networks, applications, and database events. In addition, Operations can leverage already correlated SNMP events from NNM to offer even stronger distributed event correlation, resulting in even less network traffic.

Top Visited
 Switchboard
Latest
Past week
Past month

NEWS CONTENTS

Old News ;-)

[Nov 09, 2010] IT Resource Center forums - Event Correlation in Operations Manager 9.x (linux)

Oct 28, 2010

Yashodhara Gupta:

I have completed integration of OML with NNMi9.x (linux) and ready to work on event correlation. the manual hp_man_ HPOM _CorrelationComposer_User_pdf explains the process and shows the correlation composer. I have not figured out how to open the composer. it is not part of admin GUI. Your response will be really appreciated.

Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click here

Sort Answers By: Date or Points

Goran Koruga:

Hello.

ovocomposer -ui

Regards, Goran

Vivit Discussion Groups View topic - Example of a working OVOComposer Corelator file

preston3271 Newbie

Joined: 06 Feb 2007 Posts: 5

Posted: Wed May 09, 2007 1:30 pm Post subject: Example of a working OVOComposer Corelator file

--------------------------------------------------------------------------------

Greeting all: Does anyone have a working example of a Transient Corelator that utilizes MSGTEST for the Alarm Signiture and Variable that is defined as something like clear==>constant==>"String" for the clear value.

This is how we have one of our corelators setup Alarm Signitures MSGTEXT "=" "Test Node Down" MSGTEXT "=" "Test Node Up"

Variable clear "CONSTANT" "TEST Node Up"

Adv. Alarm Signiture None

Message Key NODENAME

Parameters Window Period 2 minutes

Clear Alarm MSGTEXT "=" clear

Does this seem correct?

Also, our team leader wanted to yes if we could remove all of the Fact Store from the eco_comp to determine if this can make a difference. Is that a command option to remove *.fs files from the eco_comp? _________________ Louis Preston Thornton III Owner of It's Thornton By Design LLC. Proud Graduate of Colorado Technical University Software Engineering Program

Email: [email protected]

Back to top

Wodisch Active Member

Joined: 12 Mar 2007 Posts: 42 Location: mostly germany, occasionaly EMEA, rarely USA Posted: Wed May 09, 2007 3:53 pm Post subject: Re: Example of a working OVOComposer Corelator file

--------------------------------------------------------------------------------

Removing the fact stores is NOT a good idea, since the "OVO Composer" works like this:

The OVO Agent contains an ECS runtime (ovecsa), which is only started after at least one CS Circuit has been assigned and distributed to that node. That runtime loads the ECS Composer circuit (ecs_comp.eco). And that finally loads and interprets its fact store (ecs_comp.fs). Without the fact store you'll have NO runable OVO Composer correlation!

IT Resource Center forums - OVO Composer

Aug 17, 2006

Kiran Poovaiya:

I have the OVO composer installed and am able to create circuits for OVO but I don't know how to enable the ecs engine in OVO and run and test these circuits in a OVO environment. I have tried to distributing the composer template to the server and then deploying the circuit but it fails with the Standard error: Failed to update factstore

I have looked at several documents but they all talk about NNM,DM but not OVO or they are about ecs designer. I am looking to make this work in a OVO environment. I read in one of the doc about OS-SPI guide but cant find this. Please help.

I have looked at the following docs ECS Admin guide Correlation Composer Guide OVO Admin guide

Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click here

Ramaprasad N

Hi Kiran,

It's pretty straight forward and simple and I accept that it may not be well documented. Basically you will perform the following tasks.

Enable the Server MSI on the mgmt svr. Make sure that you have selected the option 'Divert messages'. Assign the default 'ECS template' to the mgmt server (and not the agent on the server). Distribute this configuration to the mgmt server. After this, if you perform an opcsv -status, you will see that there is a new process (opcecam) running on the mgmt svr. Then distribute the template using the ovocomposer command (hope you know the options).

I have worked on ECS composer with OVO 8.x and it just works fine with the above steps.

Let me knwo if I ican help you out with something more.

-Ram

Kiran Poovaiya:

Thanks a lot. Really helped me going. I don't not know about ovocomposer at all. All this while I have been using ovcomposer.

One quick question on a rate type of corellator templated can the AlterSpecificaion on the new alarm change the message text. Since the alarms are already in the message browser by the time count is exceeded .....

Thanks you

[Oct 14, 2010] ECS Composer Instructions

  1. To create ECS Composer template on Mgt Server (already done on hbrpsums01d6)
    1. Requires: /var/opt/OV/share/tmp/OpC_appl/comp
    2. Upload template: opccfgupld comp
    3. Fact store must exist: /var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.fs (copy from other server)
    4. Assign Composer Circuit to Mgt Server: Actions->Server->AssignTemplate
    5. Run circuit on Mgt Server: Actions->Server->Install/Update Templates (starts opcecm)
  2. To create or edit Correlation store
    1. Make sure you are running the Hummingbird Window Manager

1. Start-> Programs-> Hummingbird Connectivity 7.0-> Exceed -> Tools -> HWM

    1. Open ecs composer in developer mode: /opt/OV/bin/ovcomposer –m d
    2. Save Correlation store in /etc/opt/OV/share/conf/ecs/CIB/OpC
    3. New Correlation store will be saved with a .fs extension (fact store)
    4. Edit NameSpace.conf in that directory to add new Correlation Store
  1. To deploy Correlation store
    1. Deploy in ovcomposer –m o does not work, use command line
    2. /opt/OV/bin/csdeploy.ovpl -p /etc/opt/OV/share/conf/ecs/CIB/OpC/deploy.conf
  2. Activate Correlation store (not sure if deploy does this or not)
    1. Run: /opt/OV/bin/ecsmgr –i 11 –update \

ecs_comp /var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.fs

    1. Check: /opt/OV/bin/ecsmgr –i 11 –info or /opt/OV/bin/ecsmgr –i 11 –fact_dump
  1. IMPORTANT UPDATE (when things get screwed up)
    1. If you are unable to load a factstore execute the following:

1. /opt/OV/bin/ecsmgr -i 11 -disable ecs_comp

2. /opt/OV/bin/ecsmgr -i 11 -circuit_reload ecs_comp \ /var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.eco 0 ecs_comp

3. /opt/OV/bin/ecsmgr -i 11 -enable ecs_comp

4. /opt/OV/bin/ecsmgr -i 11 -update ecs_comp \ /var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.fs

  1. ANOTHER IMPORTANT UPDATE (severity number changes)
    1. 4 Unknown
    2. 8 Normal
    3. 16 Warning
    4. 32 Critical
    5. 64 Minor
    6. 128 Major
  2. FYI
    1. From the ecsmgr man page:

-instance <instance>

Identifies a particular engine instance when there

are multiple instances on a host system.

The default for this option is -instance 1.

pmd: The pmd-linked correlation engine is

always instance 1.

HPOM : The HPOM Server -linked correlation

engine is always instance 11.

The HPOM Agent -linked correlation engine

is always instance 12.

  1. To Create & activate Correlation store on Agent
    1. Assign & Deploy ECS Composer template to agent
    2. Edit: ENGING_INSTANCE=12 in /etc/opt/OV/share/conf/ecs/CIB/OpC/deploy.conf
    3. /opt/OV/bin/ecsmgr –i 12 –fact_update ecs_comp /var/opt/OV/conf/OpC/ecs_comp.fs

Managing Events with NNM 7.x, Operations Manager for Unix and ECS Composer

Instructor-Led Training

Detailed Course Outline

Overview

Configuring Events and Alarms in NNM

Overview System and Application Monitoring

Monitoring Logfiles

Discriminating between Log Messages

Pattern Matching

Message Interceptor and opcmsg

SNMP Trap Interceptor

Configuring Event Forwarding

Distributed SNMP Trap Management

Configuring syslog Messages for SNMP

Introduction to Event Correlation

HPOM Message Reduction

Correlating HPOM Messages with ECS and Composer

Configuring NNM Event Correlation

Introduction to Composer Development

Creating a Basic Correlator

Using Variables in Correlators

Using Additional Correlators

Relating Events from Multiple Sources

Using Callbacks and Built-In Functions

Combining Correlators

Best Practices, Tools and Information

Recommended Links

Fognet's Field Guide to OpenView ... - Google Books

Reference

ovocomposer - HPOM event correlation feature, the Correlation Composer.

Table of Contents

This man page describes the Correlation Composer, an HP Operations Manager (HPOM) event correlation feature, which makes common types of event correlations easier to develop and maintain. The Event Correlation Service (ECS) is included in HPOM. The Correlation Composer components are bundled with Network Node Manager (NNM). HPOM integrates this Composer functionality.

The critical challenge for today's network and system operators is to deal with the massive amount of information generated by monitoring network, system and application problems. This information comes in many forms, and the key to your management solution is to accurately understand what should be presented to your operators, what can be discarded, and what is needed by specialists who may need to follow a bread-crumb trail when diagnosing very complex problems.

The HP Correlation Composer (Correlation Composer) is an ECS circuit and a graphical user interface that enables you to tailor the event correlation behavior to correlations that are shipped with HP products and simplifies the development of user developed correlations. Correlations can be used out-of-the-box but can also be easily finetuned to exactly match your environment without the need for any programming knowledge.

Composer was originally released with HP Network Node Manager 6.41 and is bundled with the HP Event Correlation Services 3.2 runtime subcomponent of NNM for use with SNMP based events.

The Correlation Composer is a graphical user interface used to parameterize and create problem specific correlators. The problem specific correlators uniquely identify a unit of logic to be applied to an event or a set of events. The Correlation Composer comes prepackaged with six correlator templates that ease the creation of correlation solutions by providing correlation models for the most common correlation tasks. The pre-defined correlation templates are:

- Enhance
- Repeated
- Multi-Source
- Suppress
- Rate
- Transient

In addition to the predefined correlator templates, custom requirements can be configured using the User-Defined Correlator template.

Theory of Operations

The Correlation Composer is an extension of the Event Correlation Services (ECS) product. It is a combination of a pre-packaged ECS circuit and the graphic user interface, which used to parametrize and define Correlators to perform event correlation. It provides the following major components:

Composer Graphical User Interface

The Correlation Composer UI is used to create problem specific correlators. The problem specific correlators uniquely identify a unit of logic to be applied to an event or a set of events. The Correlation Composer comes prepackaged with six correlator templates that ease the creation of correlation solutions by providing correlation models for the most common correlation tasks.

You can launch the Composer UI using one of the following commands:

/opt/OV/bin/ovcomposer -m d -t OpC

/opt/OV/bin/OpC/ovocomposer -ui

A Correlator Store contains a set of correlators that define correlation requirements for your environment. A Correlator Store is a fact store file.

You should save your fact store files in the following location so that you can easily use HPOM applications and ovocomposer(1) to manage these stores:
/etc/opt/OV/share/conf/OpC/mgmt_sv/CO/

Composer ECS Circuit

The pre-packaged ECS Composer circuit implements the pre-defined correlation logic. This circuit is configured via a Correlator Store (a fact store), which was generated with the Composer UI.

The Composer circuit is located in the HPOM template group Correlation Composer". You have assigned and installed this ECS circuit like any other ECS Template in HPOM. Please make sure that the

Message Stream Interface (MSI) is enabled on the system where you are using the Composer circuit; on the HPOM management server system or on an HPOM managed node system. Usually, you will use the MSI in divert mode.

In HPOM, during runtime, you must have one specific fact store file for each ECS circuit. The association between an ECS circuit, a fact store name, and a fact store file is done through the basename of the circuit file and fact store file. Since the ECS Composer circuit file name is ecs_comp.eco, the fact store file with the correlators must have the name ecs_comp.fs. Additionally, the fact store file ecs_comp.fs must be located in a specific directory. These directories are:

Management Server:
/var/opt/OV/conf/OpC/mgmt_sv/
HPOM 8 HP-UX and Solaris agent:
/var/opt/OV/conf/eaagt/
HPOM 8 Windows agent:
C:\Program Files\HP OpenView\Data\conf\eaagt OVO 7 HP-UX and Solaris agent:
/var/opt/OV/conf/OpC/
OVO 7 Windows agent:
C:\usr\OV\conf\OpC\ecs_comp.fs

You can manually activate correlators by uploading the fact store with the ecsmgr(1m) tool as follows:

Management Server:
ecsmgr -i 11 -fact_update ecs_comp
/var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.fs UNIX agents:
ecsmgr -i 12 -fact_update ecs_comp
/var/opt/OV/conf/eaagt/ecs_comp.fs

You can use the ecsmgr(1m) tool to:

* Check if the Composer Circuit and fact store are loaded.

* Dump the content of the currently loaded fact store if you want to verify the actual configuration.

Refer to the ecsmgr(1m) options -info and -fact_dump.

NOTE: The Composer Circuit aborts if it is started without a valid Correlator Store (ecs_comp.fs) in the predefined location. In this case, you have to either restart the HPOM agent/server or reinstall the EC Circuit after you installed a Correlator Store.

HPOM contain applications for managing Correlator Stores and launch the Composer UI from the HPOM Application bank. The following applications are located in the application group OV Composer".

Composer UI (Dev):
This application starts HP Correlation Composer UI in Developer's mode. You should save your Correlator Stores (fact store files) in /etc/opt/OV/share/conf/OpC/mgmt_sv/CO/ so that you can use the following HPOM Applications and ovocomposer(1) to manage these stores.

Install Correlators on Server:
With this application, you install Correlator stores on the HP Operations Management Server. You will be prompted to specify Correlator stores you would like to install.

Install Correlators on Agents:
This application installs Correlator stores on HPOM Agents. You will be prompted to specify Correlator stores you would like to install on all selected nodes.

These applications call ovocomposer(1) and this tool merges multiple fact stores files into one file (ecs_comp.fs) in case you select more than one Correlator store for the installation. In some cases, you will be prompted to resolve conflicts.

USING COMPOSER WITH HPOM
You should consider the following steps when using HP Composer with HPOM:

* Prepare your management server or agent system, depending on where you would like to perform event correlation with HP Composer.

* Developing Correlators with the HP Composer UI.

* Install Correlators on your management server or agent system.

Prepare your management server or agent

Depending on where you would like to apply Correlators, you have to assign and distribute the HP Composer EC Template. To ensure that messages are passed into the Composer EC circuit, you enable the Message Stream Interface (MSI). On the management server, you can define that all messages should be diverted to the MSI. For correlation on the agent you must set the MSI options in the message conditions of the message source templates.

Before you assign and distribute the HP Composer EC Template, you should install the empty Correlator store empty.fs on your management server or agent system, because the Composer circuit cannot run without a Correlator store. Use ovocomposer(1) or the HPOM Application Install Correlators to install the Correlator store empty.fs. Please ignore the failure message Cannot connect to engine of ecsmgr(1m). This failure appears when you try to upload a fact store and the opceca or opcecm is not running yet.

Assign and distribute the HP Composer EC Template with the HPOM Administrator UI.

Developing Correlators with the HP Composer

A typical configuration of the Correlator Store involves defining the various Correlation Templates, parameters and messages required as input to the circuit. You should copy an existing Correlator store (i.e. /etc/opt/OV/share/conf/OpC/mgmt_sv/CO/) for your work so that you benefit from the already defined global constants for HPOM message attributes.

The basic task flow to create a Correlator is that you first enter name and description, provide an alarm signature for messages, declare variables and a message key, and finally, depending on the Correlator Template, specify new or altered messages.

You save your Correlators in a Correlator Store, which is physically a fact store file. Save this files in
/etc/opt/OV/share/conf/OpC/mgmt_sv/CO/ so that you can use the HPOM Applications and ovocomposer(1) to manage these stores.

For further information about using the HP Composer and developing Correlators, see HP Correlation Composer's Guide.

Install Correlators to your management server

You can install Correlator Stores on your management server or agent system in several ways. You use either the HPOM application for HP Composer, the command line tool ovocomposer(1), or do it manually. The common goal is to put the Correlator Store at the runtime location of the HPOM event correlation manager or agent and upload the Correlator Store (fact store file) using ecsmgr(1m). NOTE: The fact store file must be renamed to ecs_comp.fs. In case you want install multiple Correlator Stores to one target, you have to merge these stores using the command line tool csmerge(1M). ovocomposer(1) and the HPOM application for HP Composer will perform required merges automatically.

Directories and files

Runtime Correlator Store file:

Management Server:
/var/opt/OV/conf/OpC/mgmt_sv/ecs_comp.fs

HPOM 8 HP-UX and Solaris agent:
/var/opt/OV/conf/eaagt/ecs_comp.fs
HPOM 8 Windows agent:
C:\Program Files\HP OpenView\Data\conf\eaagt\ecs_comp.fs OVO 7 HP-UX and Solaris agent:
/var/opt/OV/conf/OpC/
OVO 7 Windows agent:
C:\usr\OV\conf\OpC\ecs_comp.fs
Central Correlator store directory on the Management Server: /etc/opt/OV/share/conf/OpC/mgmt_sv/CO/
Correlator store with HPOM specific constants: /etc/opt/OV/share/conf/OpC/mgmt_sv/CO/empty.fs Merge tool for Correlator stores:
/opt/OV/contrib/ecs/csmerge.ovpl
Migrate tool for Correlator stores:
/opt/OV/contrib/ecs/csmigrate.ovpl
Directory for files which contain Perl callback functions: /opt/OV/contrib/ecs/external/perl/

See Also

HP Operations Manager for UNIX: Concepts Guide, HP Operations Manager for UNIX: Administrator's Reference, HP Correlation Composer's Guide,
ovocomposer(1),
csmerge(1M),
csmigrate(1m),
ecsmgr(1m)

ovocomposer was developed by Hewlett-Packard Company.

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

 You can use PayPal to to buy a cup of coffee for authors of this site

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019