6 More Discussions You Might Find Interesting
1. AIX
Hi,
I need to increase a filesystem from around 1TB to 15TB on a running AIX7.1 TSM server.
This will be by far the largest single filesystem increase I've ever performed, or even heard of.
The volume group already has enough disk available (in fact the filesystem was always intended to be... (10 Replies)
Discussion started by: alanp36
10 Replies
2. AIX
How many Core in AIX6 & AIX7 ..
Please guys I want commands to know how many Core in these two different version please i need exact command ? (2 Replies)
Discussion started by: top.level
2 Replies
3. UNIX for Dummies Questions & Answers
I'd put together a zshrc for use on Linux & AIX 5/6 at another shop that worked fine, but when I tried to put it on here it messes up the colors for some reason I can't understand.
I used Phil's ZSH prompt for starters, and everything worked before, and still does on Linux, but isn't working on... (0 Replies)
Discussion started by: Vryali
0 Replies
4. AIX
Hi,
anyone know if Oracle Database 10g is AIX 7 certified???
thanks in advance.
Regards.
Mario (2 Replies)
Discussion started by: Zio Bill
2 Replies
5. AIX
Hi,
im new here and i have too admit, fairly new not to Unix in general but to AIX in specific.
I have here a DS3512 SAN, connected by Fiber Channel to a Power 720 Express, running AIX 7.1
The DS3512 has been running for some time now with 6 drives configures as 3 Raid1-Arrays, with no... (0 Replies)
Discussion started by: cricharz
0 Replies
6. Programming
Hello,
I am strugglign with the following fastcgi C++ program with access to a postgresql database through the SOCI library. All the components work individually properlyy but the combination does not. The program compiles fine but the Apapche 2.2 error log files contains:
FastCGI: comm... (0 Replies)
Discussion started by: JCR
0 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 $