Beim Einrichten eines Webservers habe ich mir Gedanken gemacht zur Direktive ‚FastCGIExternalServer‘. Auf hunderten von Seiten wird sie referenziert und verwendet, aber nirgendwo die Funktion oder die Parameter erklärt.

Hier ist die fehlende Dokumentation nun:

 

 

FastCgiExternalServer

Syntax:	FastCgiExternalServer filename -host hostname:port [option ...]
	FastCgiExternalServer filename -socket filename [option ...]
Context:	server config

The FastCgiExternalServer directive defines filename as an external FastCGI application.  If filename does not begin with a slash (/) then it is assumed to be relative to the ServerRoot.  The filename does not have to exist in the local filesystem.  URIs that Apache resolves to this filename will be handled by this external FastCGI application..

External FastCGI applications are not started by the process manager, they are presumed to be started and managed „external“ to Apache and mod_fastcgi.  The FastCGI devkit provides a simple tool, cgi-fcgi,  for starting FastCGI applications independent of the server (applications can also be self-starting, see the devkit).

-appConnTimeout n (0 seconds)Unix: The number of seconds to wait for a connection to the FastCGI application to complete or 0 to indicate a blocking connect() should be used.  Blocking connect()s have an OS dependent internal timeout.  If the timeout expires, a  SERVER_ERROR results.  For non-zero values, this is the amount of time used in a select() to write to the file descriptor returned by a non-blocking connect().  Non-blocking connect()s are troublesome on many platforms.  See also -idle-timeout, it produces similar results but in a more portable manner.
Windows NT: TCP based applications work as above.  Named pipe based applications (static applications configured without the -port option and dynamic applications) use this value successfully to limit the amount of time to wait for a connection (i.e. its not „troublesome“).  By default, this is 90 seconds (FCGI_NAMED_PIPE_CONNECT_TIMEOUT in mod_fastcgi.h).-idle-timeout n (30 seconds)The number of seconds of FastCGI application inactivity allowed before the request is aborted and the event is logged (at the error LogLevel).  The inactivity timer applies only as long as a connection is pending with the FastCGI application.  If a request is queued to an application, but the application doesn’t respond (by writing and flushing) within this period, the request will be aborted.  If communication is complete with the application but incomplete with the client (the response is buffered), the timeout does not apply.-flush noneForce a write to the client as data is received from the application.  By default, mod_fastcgi buffers data in order to free the application as quickly as possible.-host hostname:port
noneThe hostname or IP address and TCP port number (1-65535) the application uses for communication with the web server. The -socket and -host options are mutually exclusive.-pass-header header noneThe name of an HTTP Request Header to be passed in the request environment.  This option makes available the contents of headers which are normally not available (e.g. Authorization) to a CGI environment.-socket filename noneUnix: The filename of the Unix domain socket the application uses for communication with the web server.  The filename is relative to the FastCgiIpcDir.  The -socket and -port options are mutually exclusive.Windows NT:  The name of the named pipe the application uses for communicating with the web server. the name is relative to the FastCgiIpcDir.  The –socket and  -port options are mutually exclusive.

If you need to fiddle around with PARALLEL_MAX_SERVERS you will find millions of pages, describing its use and how to set it but you won’t find the hint on how to read it…until now:


select name, value, isdefault, isses_modifiable, issys_modifiable,isinstance_modifiable, isdeprecated, description from v$parameter where upper(name) = 'PARALLEL_MAX_SERVERS';

Recently I’ve been asked to boot an AIX system into 32 bit mode. Switching back and forth between 32 and 64 bit is quite easy with AIX. You need to create a link to the corresponding kernel. Officially IBM advises to boot into service mode first but it’s also possible without that step.

First check which kernel is currently running:
bootinfo -K

To boot from 64 bit into 32 bit:
ln -sf /usr/lib/boot/unix_mp /unix
ln -sf /usr/lib/boot/unix_mp /usr/lib/boot/unix
bosboot -ad /dev/ipldevice
shutdown -r

To boot from 64 bit into 32 bit:
ln -sf /usr/lib/boot/unix_64 /unix
ln -sf /usr/lib/boot/unix_64 /usr/lib/boot/unix
bosboot -ad /dev/ipldevice
shutdown -r Weiterlesen →

In case you want to install WebSphere 5.1 on a fresh SLES9 and the installation routine hangs with a

Searching for Java(tm) Virtual Machine...
.

in the console, then try the following before executing the installation routine:

export LD_ASSUME_KERNEL=2.2.5