Hi you all, I have a BIG performance problem on an Sun E3500, the scenario is described below:
I have several users (30) accessing via samba to the E3500 using an application built on Visual Foxpro from their Windows PC , the problem is that the first guy that logs in demands 30% of the E3500... (2 Replies)
Hello,
i have a a1000 connected to an e6500. There's a raid 10 (12 disks) on the a1000.
If i do a
dd if=/dev/zero of=/mnt/1 bs=1024k count=1000
and then look at iostat it tells me there's a kw/s of 25000.
But if i do a
dd of=/dev/zero if=/mnt/1 bs=1024k count=1000
then i see only a... (1 Reply)
Hello,
I'm running a script on AIX to process lines in a file. I need to enclose the second column in quotation marks and write each line to a new file. I've come up with the following:
#!/bin/ksh
filename=$1
exec >> $filename.new
cat $filename | while read LINE
do
echo $LINE | awk... (2 Replies)
Hello all
We just built a storage cluster for our new xenserver farm. Using 3ware 9650SE raid controllers with 8 x 1TB WD sata disks in a raid 5, 256KB stripe size.
While making first performance test on the local storage server using dd (which simulates the read/write access to the disk... (1 Reply)
Hello,
we have a machine with Solaris Express 11, 2 LSI 9211 8i SAS 2 controllers (multipath to disks), multiport backplane, 16 Seagate Cheetah 15K RPM disks.
Each disk has a sequential performance of 220/230 MB/s and in fact if I do a
dd if=/dev/zero of=/dev/rdsk/<diskID_1> bs=1024k... (1 Reply)
Hello guys,
I have two servers performing the same disk operations. I believe one server is having a disk's impending failure however I have no hard evidence to prove it. This is a pair of Netra 210's with 2 drives in a hardware raid mirror (LSI raid controller). While performing intensive... (4 Replies)
Hi
We have an M3000 single physical processor and 8gb of memory running Solaris 10. This system runs two Oracle Databases one on Oracle 9i and One on Oracle 10g.
As soon as the Oracle 10g database starts we see an immediate drop in system performance, for example opening an ssh session can... (6 Replies)
Hi Everyone,
I have been struggling for few days with iSCSI and thought I could get some help on the forum...
fresh install of AIX7.1 TL4 on Power 710, The rootvg relies on 3 SAS disks in RAID 0, 32GB Memory
The lpar Profile is using all of the managed system's resources.
I have connected... (11 Replies)
Just a quick note for macOS users.
I just installed (and removed) Parallels Desktop 15 Edition on my MacPro (2013) with 64GB memory and 12-cores, which is running the latest version of macOS Catalina as of this post. The reason for this install was to test some RIGOL test gear software which... (6 Replies)
Discussion started by: Neo
6 Replies
LEARN ABOUT SUSE
cgi-fcgi
NAME
cgi-fcgi - bridge from CGI to FastCGI
SYNOPSIS
cgi-fcgi -f cmdPath
cgi-fcgi -bind-connect connName
cgi-fcgi -start -connect connName appPath [nServers]
cgi-fcgi -connect connName appPath [nServers]
DESCRIPTION
cgi-fcgi is a CGI/1.1 program that communicates with an
already-running FastCGI application in order to respond to
an
HTTP request. cgi-fcgi is also capable of starting a FastC-
GI
application.
When you invoke cgi-fcgi as
cgi-fcgi -f cmdPath
then cgi-fcgi opens the file at cmdPath and reads its
arguments from that file. cgi-fcgi will skip lines
that begin with the comment character #. The first
non-comment line should contain valid arguments in
one of the other three forms.
The -f form of cgi-fcgi is designed for Unix systems
whose exec(2) family of system calls supports the execution
of
command interpreter files. For instance, if a file with
execute permission contains the text
#! /bin/cgi-fcgi -f
-connect /httpd/root/sock/app /httpd/root/bin/app
the effect is the same as executing
/bin/cgi-fcgi -connect /httpd/root/sock/app
/httpd/root/bin/app
When you invoke cgi-fcgi as
cgi-fcgi -bind -connect connName
the connName argument is either the path name of a Unix do-
main
listening socket or a host:port pair. If connName contains
a colon, it is assumed to be host:port. cgi-fcgi performs
a connect(2) using connName. If the connect succeeds, cgi-
fcgi
forwards the CGI environment variables and stdin data to the
FastCGI application, and forwards the stdout and stderr data
from
the application to cgi-fcgi's stdout (most likely connected
to
a Web server). When the FastCGI application signals the end
of
its response, cgi-fcgi flushes its buffers and
exits, and the Web server completes the http response.
When you invoke cgi-fcgi as
cgi-fcgi -start -connect connName appPath [nServers]
then cgi-fcgi performs the function of starting one or more
FastCGI application processes. The connName argument speci-
fies
either the path name of the Unix domain listening socket
that
cgi-fcgi will create, or is "localhost:NNN" where NNN is the
port
number of the TCP/IP listening socket that cgi-fcgi will
create
on the local machine. (cgi-fcgi will not create processes
on remote machines.) After cgi-fcgi creates the listening
socket,
it forks nServers copies of a process running the executable
file
appPath. If nServers is omitted, the effect is as if the
value "1"
had been specified. The processes share the single listen-
ing socket.
When you invoke cgi-fcgi as
cgi-fcgi -connect connName appPath [nServers]
cgi-fcgi performs -bind and then, if necssary, performs
-start
and repeats the -bind. That is, cgi-fcgi first operates as
if
the command had been
cgi-fcgi -bind -connect connName
If the connect fails, cgi-fcgi tries
cgi-fcgi -start -connect connName appPath [nServers]
and finally retries
cgi-fcgi -bind -connect connName
In this form, cgi-fcgi does not support TCP/IP connections.
ENVIRONMENT VARIABLES
The usual CGI ones, but they are not interpreted by cgi-fc-
gi.SEE ALSO FGCI_accept(3)BUGS
cgi-fcgi doesn't generate useful HTTP responses in case of
error,
and it generates no response at all when run as start-fcgi.
On Digital UNIX 3.0 systems the implementation of Unix Do-
main
sockets does not work when such sockets are stored on NFS
file
systems. Symptom: cgi-fcgi may core dump or may exit with
status 38. Work-around: store sockets in local file systems
(/tmp often works) or use TCP/IP.
On AIX systems the implementation of listening sockets
does not support socket sharing, and the standard FastCGI
application libraries can't synchronize access to AIX lis-
tening
sockets. Work-around: Don't use the nServers argument on
AIX.HISTORY
Copyright (c) 1996 Open Market, Inc.
See the file "LICENSE.TERMS" for information on usage and
redistribution
of this file, and for a DISCLAIMER OF ALL WARRANTIES.
$Id: cgi-fcgi.1,v 1.1.1.1 1997/09/16 15:36:26 stanleyg Exp $