[Orca-users] case sensitivity?

[Saladin, Miki]

this is a great answer - and i have (Of course) have just a few more. 

i need to know, before i implement WEB_SERVER_SECURE=HTTP,i'd like to
ascertain the effects on any other web graphs.   



1. Number of System & Web Server Processes - will processes counted by
WEB_SERVER_SECURE be added to this graph?
2. Number of Web Server Processes - i assume the WEB_SERVER_SECURE will not
be added to this graph - it will have a separate one?

both flavor of the http and HTTP use the same access_log so i 'm not sure
about the effects on the following but would like to know -  

3. Web Server Hit Rate - ?
4. Web Server File Size  - ?
5. Web Server Data Transfer Rate - ? 
6. Web Server HTTP Error Rate - ? 


-----Original Message-----
From: Blair Zajac [mailto:blair at orcaware.com]
Sent: Monday, December 08, 2003 8:23 PM
To: Saladin, Miki
Cc: 'orca-users at orcaware.com'
Subject: Re: [Orca-users] case sensitivity?


"Saladin, Miki" wrote:
> 
> in the start up script for orcallator i have
> 
> WEB_SERVER="httpd"
> 
> will that detect both upper case and lower case http?
> i have both.

The orcallator.se script uses SE's =~ operator to do regular
expression matches on process names.

I don't believe this operator is case insensitive.

A work around is to edit start_orcallator.sh:

# WEB_SERVER_SECURE contains a regular expression used to find the
# number of running secure web server processes on the system.
WEB_SERVER_SECURE=httpsd

and set WEB_SERVER_SECURE to the uppercase version of the name.
It'll come out in the orcallator data files as #httpsds instead
of #httpds so you'll get separate data for them, which may be
a good thing or not, depending upon what you want to do.

If you want, you could always edit

count_procs()

in orcallator.se to change the =~ to a case insensitive compare.

Best,
Blair

-- 
Blair Zajac <blair at orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/