I2OCFG(8)

NAME
i2ocfg - I2O configuration dialog gateway

SYNOPSIS
i2ocfg

DESCRIPTION
i2ocfg is a CGI (Common Gateway Interface) program that sits between a HTTP server and an IOP (I/O processor), passing data between the two.

A `configuration dialog' is, in short, I2O nonclemanture for a human user requesting one or more HTML pages from a device. Optionally, HTML form data may also be included in each request.

i2ocfg accepts two kinds of paths. The first form (no path, or a single ``/'') requests the index page. The index page lists each IOP in the system, and the devices controlled by each IOP. The second form requests a configuration dialog with a specific device. It looks like this:

    	/iop#/tid#/page#?var1=val1&var2=val2

Requesting page 0 returns the index page for that device. Note that the I2O executive (the controlling force behind the IOP) is located at TID 0.

For example, the following path requests the index page from the executive on iop0:

    	/0/0/0

FILES
/dev/iopu
    control device for IOP unit u

SEE ALSO
ioctl(2), iop(4), iopsp(4), ld(4), iopctl(8)

AUTHOR
i2ocfg was written by Andrew Doran <ad@netbsd.org>.

BUGS
This should be re-implemented as a client/server pair. Re-opening the control device for each request is expensive; furthermore, it may not be desirable to run a web server on the same host on which the target IOP(s) reside(s).

Not all I2O implementations support configuration dialogs.