invscoutd Command

Purpose

Launches a permanent Inventory Scout server daemon.

Syntax

invscoutd [ -o] [ -p Portno ] [ -b Bufsize ] [ -d maxcatsize ] [ -t Timeout ] [ -v Verblev ]

Description

The invscoutd command implements a permanent Inventory Scout server daemon on one machine in the local network of the user. The usual client is a Java applet running in the Web browser of the user, which was downloaded from a central Inventory Scout CGI application.

Daemon initialization involves reading command line options and several local Inventory Scout companion files. When in operation, each client-server transaction involves reading from a well-known socket for a text string and returning a text report over the same socket.

The daemon maintains a record of its actions in a log file. Depending on the specified verbosity level, the log lines may contain startup and shutdown banners, traces of each call, detailed internal program traces, and error statements. Depending on the specified verbosity level, startup banners may also be written to stderr.

Protocols

Client connections to the daemon's socket use the Internet TCP/IP protocol. In a transaction, the invoking client applet sends an action request, as a URL-encoded text string, to the server daemon. The request is by any ASCII control character (x00 to x1F), which triggers the processing of the request.

Some requests require the client to pass additional data. In these cases, the additional data immediately follow the termination byte for a length specified in the action request.

With one exception (ACTION=PING), the server daemon always returns a pseudo MIME format text report written back over the same socket connection. The pseudo MIME format is used even for error results. The daemon terminates the returned text and the transaction itself by closing the socket, resulting in an end-of-file (EOF) indication to the invoking client. The client should close the socket at its end of the connection as soon as the EOF is received.

URL-encoded message

"ACTION=actionword&NAME1=value1&NAME2&NAME3=word%xx+word+word\0"

"action=ping\0"

<EOF>

"action=ECHO&MRDM=xyz&datalen=5\0abcde"

"RESULT=0\n"
"\n"
"action=ECHO&MRDM=xyz&datalen=5\n"
"abcde"<EOF>

"action=UrlDecode&subaction=xyz\0"
 

"RESULT=0\n"
"\n"
"  0: ACTION       UrlDecode\n"
"  1: SUBACTION    xyz\n"
<EOF>

"ACTION=TESTPWD&MRDM=thepassword\0"
 
"RESULT=0\n"
"\n"
<EOF>

"ACTION=VERSIONS\0"
 
"RESULT=0\n"
"\n"
"1.2.3.4\n"
"5.6.7.8\n"
<EOF>

"ACTION=CATALOG&MRDM=xyz&DATALEN=17042\0"
"...17042 bytes of ascii data..."

"RESULT=0\n"
"\n"
<EOF>

"ACTION=MCODES&MRDM=xyz\0"
 
"RESULT=0\n"
"\n"
"Report Line 1\n"
"Report Line 2\n"
    :
    :
"Report Line N\n"
<EOF>

"ACTION=VPDS&MRDM=xyz\0"
 
"RESULT=0\n"
"\n"
"Report Line 1\n"
"Report Line 2\n"
    :
    :
"Report Line N\n"
<EOF>

Results

The daemon returns a text result in a pseudo MIME format. It returns a header consisting of one or more Name=Value pairs, each on a line by itself. The first Name=Value pair always is the result code in the form RESULT=number. The result code is always returned for every action, except for the PING action.

Internal scout result codes applicable only to the Java applet client are not documented in the following information.

An optional free-form text report may follow the header lines depending on the result code. If there is a free-form text report, the header is first terminated by an empty line, such as two adjacent linefeeds.

In any event, the result report is terminated by an EOF indicator after reading the last of the report text from the socket. The EOF also signifies the end of the transaction itself.

Flags

Specify any arguments, beginning with a hyphen (-). Space is not allowed between a flag and its value.

Exit Status

This command returns the following exit values:

Security

The daemon must execute as effective user ID 0 (root). It is owned by root, and is installed with the "setuid" bit ON so that any user can launch it. At certain execution points, however, service children of the daemon reset their user ID to the authentication user ID invscout. The daemon does not execute unless the user invscout has been created on the host system.

By default, an accompanying cleartext password is required from the client for most operations. If the client's password does not match the system password for the authentication user ID invscout, the action exits with a return code. The authentication user ID cannot be changed.

Files