Re: Why Does conserverd grap a tty for each connection?

Quoting "Matott, Scott" <Scott.Matott@htc.com>:
> Connecting to the telnet port will give you serial console on the
> machine plugged into the corresponding serial port on the Annex.

Good.

> conserver's built in 'network connection' setting wouldn't work, not
> sure why, but no problem, instead I used to the | option to execute an
> arbitray command, in this case telnet, so my conserver.cf lines look
> like this:
> 
> conanx2-port61:| /usr/bin/telnet conanx2-port61::conanx2-port61.log:
> 
> Works great.

That's good, but the network port stuff should work just as well...actually, 
better 'cause it won't chew up the pseudo-ttys (telnet usually requires a 
psuedo-tty for it to even function).

If you use:

conanx2-port61:!conanx2-port61:23:&.log:
conanx2-port62:!conanx2-port62:23:&.log:

etc, does it not work?  I'm assuming I got the naming convention right...but 
that should open port 23 connections to each of those hostnames with logfiles 
of the form conanx2-port61.log, conanx2-port62.log, etc.

I'm going to ignore the whole pseudo-tty problem 'cause getting it to open it's 
own TCP connections directly to port 23 will be a whole lot better in the long 
run for you.  Trust me...less processes, psuedo-ttys, memory, etc.  Plus 
the '!' syntax code is used by myself instead of the '|' syntax...so I know it 
works (but the '|' syntax works as well...just not quite as well on all 
platforms).  Anyway, if you can let me know what happens with lines like above, 
I'd love to hear about it.  It really should "just work".

Bryan