[9fans] ndb/cs

[Lucio De Re <lucio@proxima.alt.za>]

I really am too frightened to look at the source, but an educated
guess leads me to believe that an inconsistency in the function of
ndb/cs is responsible for the lack of resolving in the names of the
"il" ports in netstat(1).

I wrote a simple test program, then double checked by using
ndb/csquery (the latter may not be all that indicative).

Basically, a csgetval(2) called as follows:
	csgetval ("net", "port", "566", "il", buf);
returns a failure because, apparently, the request to /net/cs stops at
the first entry (port=566 tcp=guard).  The actual value returned by
csetval(2) seems to contain _only_ the above entry.

I won't insult anyone (or embarrass myself) by posting the 20 lines of
so or code, unless it's the only way to prove my point (or embarrass
myself :-).

++L