the log file (NOT run file) if time-stamp-interval seconds have passed
since the last write to the logfile.

Major lint cleanup: remove HPBSD code, prototypes, varargs, ...

home without worrying about ssl/capserv/acl stuff.

condition that was probably caused by unexpected parallelism.

One semantic change is that we used to block SIGTERM (but not SIGINT, which
also would quit) during read/write operations.  I don't do that anymore,
so if you kill capture, the log could lose some console output.

Changed default path, made it a #define.

boss.

To tip (or tiptunnel on a normal acl,) capture behaves the same.
However, if a client connects and presents "USESSL" as the first six characters of their
connection key, both sides initiate SSL negotiation.
The server then attempts to get the key again. The second one is used for the check.

SSL initialization is done on the first attempt by a client to connect via SSL.
Capture assumes $(prefix)/etc/capture/cert.pem contains its certificate unless
the '-c <certfile>' option is used.. if the certificate is not found or invalid, that
connection fails, but normal connections will still succeed (and it will try to find the file
again, next time an SSL connection is attempted.)

On the client side, tiptunnel only uses ssl if there is a "ssl-server-cert:"
property in the acl file. This is the SHA hash of the certificate that the capture server is
expected to have (in hex.) If the certificate presented by the server does not hash to the
same value, the connection is dropped.

a node is not allocated (thus putting the .acl and .run file into the
wheel group when capture creates them), return the value of the config
variable TBADMINGROUP (which is flux for us). This makes it easier for
admin people to look at free nodes.

Capserver and capture now handshake the owner/group of the tipline.
Owner is defaults to root, and the group defaults to root when the
node is not allocated. Capture will do the chmod after the handshake,
so if boss is down when capture starts, the acl/run file will get 0,0,
but will get the proper owner/group later after its able to handshake.
As a result, console_setup.proxy was trimmed down and cleaned up a
bit, since it no longer has to muck with some of this stuff.

A second change was to support multiple tiplines per node. I have
modified the tiplines table as such:

	| Field   | Type        | Null | Key | Default | Extra |
	+---------+-------------+------+-----+---------+-------+
	| tipname | varchar(32) |      | PRI |         |       |
	| node_id | varchar(10) |      |     |         |       |
	| server  | varchar(64) |      |     |         |       |

That is, the name of the tip device (given to capture) is the unique
key, and there can be multiple tiplines associated with each node.
console_setup now uses the tiplines table to determine what tiplines
need to be reset; used to be just the name of the node_id passed into
console_setup. Conversely, capserver uses the tipname to map back to
the node_id, so that it can get the owner/group from the reserved
table.

I also removed the shark hack from nalloc, nfree, and console_reset,
since there is no longer any need for that; this can be described
completely now with tiplines table entries. If we ever bring the
sharks back, we will need to generate new entries. Hah!

ack/nak for a connection so that the connecting process knows what the
hell is going on. Turned out to be necessary for power control since
we do that in parallel, and because it stays busy for 10 seconds on
each power control. I think we will end up revisiting this at some
point, adding blocking connections instead of connect/fail status.

Apparently I forgot to commit this long ago.

older tty version at the same time. We use that older version outside
the testbed.

is actually used anymore.
Added a "generic" entry to /etc/remote so that we do not need tip
entries for each node; they all look the same anyway.
Change tip to lookup up generic /etc/remote entry, just to make
tip happy. The acl file comes from the tiplogs directory, as
set in the header file.

down.

distributed tiplines (and capture processes).

of pty/tty based (since they have several annoying problems
associated). Note that permission is granted via the use of an "acl"
file; /dev/tip/machine.acl, which must be set to the group of the
project the node is in, so the user can read out the process id number
and the random bits that are used by capture to grant permission to
use (tip sends the random bits across first thing). This handshake is
due to change to a request/challenge scheme as described by Dave in
email to the testbed list.

Standardized error message format

mode correct.  It works now.  Really.

Set non-blocking write the correct way this time!

2. Add pty flush and revoke on a shutdown (USR2) signal
3. cleanups

code I found in /foo/x/mike/src/capture/capture.c. Second, add a -r
option to open up a second log file called the "run" file, which is
intended to be used for the experiment session log. This log is
restarted with a SIGUSR1. Third, add SIGUSR2 handler to close the
pty side of the capture, which has the nice side effect of causing tip
to exit gracefully.

Note that this has a hardcoded value for NBPG, a define that's only
present in the digiboard headers.  In the interest of minimal source
code changes (heh, heh, heh) I left it alone. :p

Works on *bsd, and now Linux.  Manpage included at no charge,
though if someone wants to figure out why the manpage only
works under BSD ("Because Dave is an idiot" is not an acceptable
answer, true as it may be), that'd be cool.