12-20-2011
AIX 5.1 and RS6000
I've an old server 1996 RS6000 (Processor 604e) running AIX 5.1.
It started up fine, booted up and connected on 10Mbit with my router. I used to be able to connect to it with telnet but not anymore. I know the IP is right but working with the smit tcpip options, looks like I've changed something as I can't access any of the ports.
I've two 9 pin serial connector adapters at the back that I presume are the HMC connectors in those days but I have no HMC to connect this desktop too on my end.
The only thing I have available for this system is a network cable and power cable. I don't have a keyboard or monitor for it nor a video card to hook up some sort of terminal to debug from the console. With IBM AIX being hardware specific, it's tough to find ones appropriate for IBM and such an old RS6000.
Is there any other way to get into the system now and recover from this?
10 More Discussions You Might Find Interesting
1. Programming
I am looking for the above
Can anyone point me to a reliable product, with available
support in the forseeable future ?
Seeker (0 Replies)
Discussion started by: Seeker
0 Replies
2. UNIX for Advanced & Expert Users
I am attempting to install PHP on an IBM RS6000 AIX UNIX box. I am not getting very far and hope someone can point me in the right direction. Here is the message from the output:
checking for Apache 1.x module support via DSO through APXS
Sorry I was not able to successfully run APXS.... (6 Replies)
Discussion started by: jyoung
6 Replies
3. UNIX for Advanced & Expert Users
Hello all!
This is my first post here!
I'm having a hard time with an IBM RS/6000 J40 machine.
I'm trying to install AIX 5.2L on it but, up to now, I can't make it boot from the CDROM.
Do any of you have an ideia?
Thank you for your time! (3 Replies)
Discussion started by: MCM
3 Replies
4. AIX
Hello there!
I have a RS-6000 7043-140 machine with AIX version 4.1.5, that is
working for almost 8 years now. It has a tty monitor. My problem
started when I upgraded my machine to install a gxt250 graphics adapter
card together with a 15" AOC VGA Monitor, logitech keyboard and mouse, ... (2 Replies)
Discussion started by: bright_genius
2 Replies
5. AIX
Hi There!!
I need to reinstall the operating system AIX 5.2 in a RS6000 7026/6H1 that has AIX 4.3 but I need a firmware upgrade that I dón´t know where can I obtain.
- Platform firmware version 3 or later.
Someone can help me please, I will be very grateful !!
Thank´s. (1 Reply)
Discussion started by: terron79
1 Replies
6. AIX
So im fairly new to AIX and my knowledge is very, very limited but i got my hands on an RS6000 43P model and im trying to get it on the network so i can access it from work. I have pretty much tried everything i can/know how to do by reading up as much as i can but im still lost.
I have the 43P... (2 Replies)
Discussion started by: IIIII
2 Replies
7. AIX
Hello everyone,
I have just joined your forum even though I have been using it on and off for couple of months now. Up until now I have been able to find any information I needed by just browsing this site or performing a Google search, but now I'm stuck!. I was hoping you could help me with... (16 Replies)
Discussion started by: juniorG
16 Replies
8. AIX
Greetings to all:
Gentlemen, I've tried extremely hard to hookup my notebook via the hyperterminal to my AIX box (IBM 7046-B50) by virtue of a cross-over cable. Don't know really whats going on ......to my surprise. The notebook says its hookedup successfully but shows no unix login prompt on... (6 Replies)
Discussion started by: mhatmi
6 Replies
9. AIX
Hi,
I'm at following old machine:@rs6000:/:> uname -a
AIX rs6000 2 4 007016224C00 We are facing some problems with print queues, whenever a print queue gets stuck we cannot cancel it, we don't have any other option except restarting the machine, we have following queues:@rs6000:/etc:> lpstat... (23 Replies)
Discussion started by: nervous
23 Replies
10. AIX
Hey guys,
I'm a newbie in Unix world..
Currently in my office lies an old IBM RS6000 which hasn't been maintained for a very long time. The former admin has resigned and we don't have any documentation or whatsoever regarding the old machine. All I know that it is an RS6000 is because of what's... (4 Replies)
Discussion started by: arch4ng3l
4 Replies
LEARN ABOUT DEBIAN
cgi-fcgi
cgi-fcgi(1) General Commands Manual cgi-fcgi(1)
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 FastCGI 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 char-
acter #. 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
/usr/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 domain 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 specifies 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 lis-
tening 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 listening 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-fcgi.
SEE ALSO
FGCI_accept(3).
(in Debian, /usr/share/doc/libfcgi?/*)
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 Domain 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 listening 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 DIS-
CLAIMER OF ALL WARRANTIES. $Id: cgi-fcgi.1,v 1.1.1.1 1997/09/16 15:36:26 stanleyg Exp $
1997-09-17 cgi-fcgi(1)