From mccantaj@amgen.com Mon Mar  1 10:32:35 2004
Received: from knife.amgen.com (tls1.amgen-tls.com [138.133.232.138])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i21IWWfv011121
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL)
	for <users@conserver.com>; Mon, 1 Mar 2004 10:32:33 -0800 (PST)
Received: from mailbag.amgen.com (mailhost [138.133.10.78])
	by knife.amgen.com (8.12.10/8.12.10) with ESMTP id i21IWW2k025161
	for <users@conserver.com>; Mon, 1 Mar 2004 10:32:32 -0800 (PST)
Received: from WA-BH1-SEA.immunex.com (wa-bh1-sea [10.220.226.99])
	by mailbag.amgen.com (8.8.5/8.8.5) with ESMTP id KAA08880
	for <users@conserver.com>; Mon, 1 Mar 2004 10:32:32 -0800 (PST)
Received: by WA-BH1-SEA.immunex.com with Internet Mail Service (5.5.2657.72)
	id <FLFL0XLM>; Mon, 1 Mar 2004 10:32:31 -0800
Message-ID: <567ACB2E39C83543B746F1AD7F5E5E0402F948DB@wa-mb2-sea.amgen.com>
From: "McCanta, Jay" <mccantaj@amgen.com>
To: "'users@conserver.com'" <users@conserver.com>
Date: Mon, 1 Mar 2004 10:32:30 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: -4.901 () BAYES_00
X-Scanned-By: MIMEDefang 2.39
Subject: RE: Problems with 8.1.0
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2004 18:32:36 -0000

How about some setting that will only start so many connections per unit of
time per server?  I've set my exec command to something like... 

	exec "sleep 10; /usr/local/bin/ssh -p 2210 ..."

for port 10.  I'm only doing one connection per second that way.  It's
really stabilized the startup of conserver.  We have 48 port InReach
terminal servers and it cannot initialize 48 ssh connections in short order
without hanging.

Jay McCanta
Amgen, Inc.
206-265-8335

-----Original Message-----
From: Bryan Stansell [mailto:bryan@conserver.com] 
Sent: Friday, February 27, 2004 2:41 PM
To: McCanta, Jay
Cc: 'Bryan Stansell'
Subject: Re: Problems with 8.1.0

nope...and i doubt there ever will be, since keeping up with the
protocol and not introducing security bugs, etc, would probably kill me.
i, at least, expect ssh to "just work" and i rely on openssh and that
community to keep it all honest.

i really wish there was a way to prevent all those processes, though.
if you have a couple 32 port terminal servers, you can really get a lot
of ssh processes going (and it can be hell for the terminal servers to
keep up with all it's ports doing encryption/decryption...it used to
strike fear in the vendor's hearts when you ask "can it support 32
simultaneous ssh connections?"..."how long?"..."indefinitely."..."no,
i'm serious...you see, i have this program...").

but, if you have any good ideas on how to reduce the overhead of things
or a better way to integrate ssh, i'd love to hear 'em!

Bryan

On Fri, Feb 27, 2004 at 02:23:14PM -0800, McCanta, Jay wrote:
> I am somewhat new to conserver.  I am using the "type exec" and an
external
> ssh command to connect conserver to my InReach terminal servers.  Is there
a
> native method in conserver to do this without spawning all the ssh
> processes?
> 
> Jay 
From bryan@stansell.org Thu Mar  4 05:59:51 2004
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i24DxoUu013486
	for <users@conserver.com>; Thu, 4 Mar 2004 05:59:51 -0800 (PST)
Received: (from bryan@localhost)
	by underdog.stansell.org (8.12.11/8.12.11/Submit) id i24DxohH013485
	for users@conserver.com; Thu, 4 Mar 2004 05:59:50 -0800 (PST)
Date: Thu, 4 Mar 2004 05:59:50 -0800
From: Bryan Stansell <bryan@conserver.com>
To: users@conserver.com
Message-ID: <20040304135950.GX3924@underdog.stansell.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
X-Scanned-By: MIMEDefang 2.39
Subject: anyone use conserver with vt100s?
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Thu, 04 Mar 2004 13:59:52 -0000

or do you know of anyone doing that?  specifically, the vt100 has the
PF1 through PF4 keys, which transmit '^[O' followed by either P through
S.  conserver uses P through S as alternate keys for certain sequences,
assuming someone might set the escape sequence to '^[O' and then hit PF1
through PF4.

if what i just said makes you think "heck no, doesn't sound like
anything i/we do" then you can skip to the last paragraph or just delete
this and go on with life.

now, the only real "easy" way of using this would be to either alias the
console command to 'console -e '^[O' "$@"' or override the defaults when
you build conserver...but, even if you do, does anyone use a vt100 any
more...well, specifically, the PF* keys?

yeah, i've used ascii terminals in computer rooms before (for when
things get really bad), but i've never tried emulating a vt100 and
sending the PF* keys.  '^Ec' is just too easy for me to type.

i was also thinking folks might be using an xterm (or some such) and
defining keys to send PF* sequences.  but, if you're doing that, why not
just define them to send '^Ec' sequences instead...unless it's built-in
and you're counting on it (but you still have to override the escape
sequence).

so, those are my thoughts.  what i'd like to do is remove the checks for
keys P through S and (potentially) reuse them for other functions.  but,
if there are folks actually counting on the old PF* keys, i'd like to
talk to you.  if i don't hear anything from anyone, i'll assume no one
is using this bit of mostly-undocumented code.

Bryan
From bryan@stansell.org Thu Mar 11 10:02:02 2004
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2BI22MS002272;
	Thu, 11 Mar 2004 10:02:02 -0800 (PST)
Received: (from bryan@localhost)
	by underdog.stansell.org (8.12.11/8.12.11/Submit) id i2BI22Wu002271;
	Thu, 11 Mar 2004 10:02:02 -0800 (PST)
Date: Thu, 11 Mar 2004 10:02:02 -0800
From: Bryan Stansell <bryan@conserver.com>
To: announce@conserver.com, users@conserver.com
Message-ID: <20040311180201.GE396@underdog.stansell.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
X-Scanned-By: MIMEDefang 2.39
Cc: 
Subject: conserver-8.1.2 is available
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2004 18:02:04 -0000

There's truly a mixed bag of changes in this release.  The major one is
the change to the syntax of the *subst config items.  If you're using
any of them, you'll need to update your config file.  Sorry about that,
but it's well worth it.

Here's the complete list of changes in this release...

version 8.1.2 (Mar 11, 2004):
	- better handling of client command (^Ec|) when user is bumped,
	  conserver is reconfigured, etc
	- added 'initsubst' option for 'initcmd' substitutions like
	  'devicesubst' and 'execsubst' - based on patch by Bill
	  Sommerfeld <sommerfeld@east.sun.com>
	- modified and added to *subst (initsubst, etc) syntax to allow
	  for flexibility and future enhancement
	- changed 'port' and 'portinc' minimums from 1 to 0 - it allows
	  more flexibility and helps with 0-based counting
	- removed unportable sys/cdefs.h from contrib/chat/chat.c -
	  patch by Bill Sommerfeld <sommerfeld@east.sun.com>
	- added --with-extmsgs configure switch to enable entertaining
	  messages
	- marked various undocumented client commands as depreciated so
	  that they can be removed in a future version
	- added ability to "move" to a new console via '^Ec;' -
	  suggested by Christopher T. Beers <ctbeers@syr.edu>
	- added a dump of console information when -S is used twice -
	  suggested by Todd Stansell <todd@stansell.org>

Bryan Stansell
From woods@proven.weird.com Fri Mar 12 01:33:03 2004
Received: from proven.weird.com (proven.weird.com [204.92.254.15])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2C9X1r4009105
	for <users@conserver.com>; Fri, 12 Mar 2004 01:33:01 -0800 (PST)
Received: from localhost (2100 bytes) by proven.weird.com
	via sendmail with STDIO (sender: <woods>) (ident <woods> using UNIX)
	id <m1B1j2J-0002X2C@proven.weird.com> for <users@conserver.com>;
	(dest:remote)(R=bind_hosts)(T=inet_zone_bind_smtp)
	Fri, 12 Mar 2004 04:32:59 -0500 (EST)
	(Smail-3.2.0.116-Pre 2003-Jun-18 #1 built 2004-Mar-4)
Message-Id: <m1B1j2J-0002X2C@proven.weird.com>
Date: Fri, 12 Mar 2004 04:32:59 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Face: ; j3Eth2XV8h1Yfu<eXd9JL+"t;
	iT8?{X]Fjm`Qb]>*uL{<:dQ$#E[DB0gemGZJ"J#4fH*][ lz;
	@-iwMv_u\6uIEKR0KY"=MzoQH#CrqBN`nG_5B@rrM8,f~Gr&h5a\=<t0loVf0$}bP=]i3OMh"n_
	_@m4/,
	~2`V=(-9LyW.)'`@E_fE^<4y7)BIe`A''/j-Y#gDNZERh%CCij'q-NA4F<|yjznEhd7=l^xH
	2.qD3o0IanGHERTW+z$G
From: "Greg A. Woods" <woods@weird.com>
To: "ConServer User's Mailing List" <users@conserver.com>
In-Reply-To: <20040304135950.GX3924@underdog.stansell.org>
References: <20040304135950.GX3924@underdog.stansell.org>
X-Mailer: VM 7.18 under Emacs 21.3.1
Organization: Planix, Inc.; Toronto, Ontario; Canada
X-Spam-Score: -4.901 () BAYES_00
X-Scanned-By: MIMEDefang 2.39
Subject: Re: anyone use conserver with vt100s?
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
Reply-To: ConServer User's Mailing List <users@conserver.com>
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2004 09:33:05 -0000

[ On Thursday, March 4, 2004 at 05:59:50 (-0800), Bryan Stansell wrote: ]
> Subject: anyone use conserver with vt100s?
>
> yeah, i've used ascii terminals in computer rooms before (for when
> things get really bad), but i've never tried emulating a vt100 and
> sending the PF* keys.  '^Ec' is just too easy for me to type.
> 
> i was also thinking folks might be using an xterm (or some such) and
> defining keys to send PF* sequences.

yes, some emulators faithfully mimic vt100 PF* keys (and indeed I think
even xterm can do that)

>  but, if you're doing that, why not
> just define them to send '^Ec' sequences instead...unless it's built-in
> and you're counting on it (but you still have to override the escape
> sequence).

Well the more appropriate question is whether or not anyone's using an
application which expects the user to send those sequences.

If so then one might also ask whether it's a libcurses (terminfo or
termcap) based application and whether or not the user has the ability
and skills to modify their termcap/terminfo entries as well as their
terminal emulator settings.

-- 
						Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>          Secrets of the Weird <woods@weird.com>
From bryan@stansell.org Mon Mar 22 17:23:10 2004
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2N1N6SG006961;
	Mon, 22 Mar 2004 17:23:09 -0800 (PST)
Received: (from bryan@localhost)
	by underdog.stansell.org (8.12.11/8.12.11/Submit) id i2N1N6tp006960;
	Mon, 22 Mar 2004 17:23:06 -0800 (PST)
Date: Mon, 22 Mar 2004 17:23:06 -0800
From: Bryan Stansell <bryan@conserver.com>
To: users@conserver.com, announce@conserver.com
Message-ID: <20040323012306.GW5301@underdog.stansell.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
X-Scanned-By: MIMEDefang 2.39
Cc: 
Subject: conserver-8.1.3 is available
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2004 01:23:14 -0000

Not many changes this time.  I've cleaned up some of the allocations in
the client and extended the '^Ec;' sequence slightly.  I hope you all
enjoy it.

version 8.1.3 (Mar 22, 2004):
	- fixed small memory and file descriptor leak in client when
	  using '^Ec;'
	- '^Ec;' now only disconnects from the previous console only
	  after a successfully move to a new console, allowing you to
	  abort the move - suggested by Christopher T. Beers
	  <ctbeers@syr.edu>

Bryan Stansell
From m.d.t.evans@qmul.ac.uk Tue Mar 23 01:51:49 2004
Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2N9pkMV027845
	for <users@conserver.com>; Tue, 23 Mar 2004 01:51:47 -0800 (PST)
Received: from smtp.qmul.ac.uk ([138.37.6.40])
	by mail2.qmul.ac.uk with esmtp (Exim 4.14) id 1B5iZS-0001MT-KQ
	for users@conserver.com; Tue, 23 Mar 2004 09:51:42 +0000
Received: from mdte.css.qmul.ac.uk ([138.37.8.140])
	by smtp.qmul.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 3.35 #5)
	id 1B5iZR-00072y-00
	for users@conserver.com; Tue, 23 Mar 2004 09:51:41 +0000
From: Martin Evans <m.d.t.evans@qmul.ac.uk>
To: users@conserver.com
Content-Type: text/plain
Message-Id: <1080035495.4329.18.camel@mdte>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Tue, 23 Mar 2004 09:51:35 +0000
Content-Transfer-Encoding: 7bit
X-Sender-Host-Address: 138.37.8.140
X-QM-Scan-Virus: virusscan says the message is clean
X-QM-Scan-Virus: ClamAV says the message is clean
X-Spam-Score: -4.901 () BAYES_00
X-Scanned-By: MIMEDefang 2.39
Subject: ^Ecp on login?
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2004 09:51:51 -0000

Hi,

Just a small question, is it possible to replay the last few lines
automatically when the console starts up? i.e. like ^Ecp but only 5-10
lines. Most of my machines are connected via serial lines to conserver.
When I bring up a console, as the previous output is not already there I
find I need to press \n a few times (generating a few bad logins) to get
a login prompt.

Kind regards,
Martin.

-- 
-- Dr MDT Evans, Computing Services, Queen Mary, University of London

From bryan@stansell.org Tue Mar 23 06:08:12 2004
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2NE8CCT007860
	for <users@conserver.com>; Tue, 23 Mar 2004 06:08:12 -0800 (PST)
Received: (from bryan@localhost)
	by underdog.stansell.org (8.12.11/8.12.11/Submit) id i2NE8CQ2007859
	for users@conserver.com; Tue, 23 Mar 2004 06:08:12 -0800 (PST)
Date: Tue, 23 Mar 2004 06:08:11 -0800
From: Bryan Stansell <bryan@conserver.com>
To: users@conserver.com
Message-ID: <20040323140811.GZ5301@underdog.stansell.org>
References: <1080035495.4329.18.camel@mdte>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1080035495.4329.18.camel@mdte>
User-Agent: Mutt/1.4.2.1i
X-Scanned-By: MIMEDefang 2.39
Subject: Re: ^Ecp on login?
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2004 14:08:14 -0000

you just need to use the -A, -F, or -S flag on the client to have it do
a '^Ecr' automatically.  the default action is -a, so 'console -A ...'
would probably be the most appropriate to start.

and if you wanted -A to be the default, you just need to change a couple
lines of code in console.c (hint: fReplay=1).

Bryan

On Tue, Mar 23, 2004 at 09:51:35AM +0000, Martin Evans wrote:
> Hi,
> 
> Just a small question, is it possible to replay the last few lines
> automatically when the console starts up? i.e. like ^Ecp but only 5-10
> lines. Most of my machines are connected via serial lines to conserver.
> When I bring up a console, as the previous output is not already there I
> find I need to press \n a few times (generating a few bad logins) to get
> a login prompt.
> 
> Kind regards,
> Martin.
> 
> -- 
> -- Dr MDT Evans, Computing Services, Queen Mary, University of London
> 
> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users
From pgeenhuizen@carolina.rr.com Fri Mar 26 04:29:19 2004
Received: from ms-smtp-01-eri0.southeast.rr.com
	(ms-smtp-01-lbl.southeast.rr.com [24.25.9.100])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2QCTFua029597
	for <users@conserver.com>; Fri, 26 Mar 2004 04:29:18 -0800 (PST)
Received: from homeunix.net (clt25-91-086.carolina.rr.com [24.25.91.86])
	by ms-smtp-01-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id
	i2QCTCSm005024
	for <users@conserver.com>; Fri, 26 Mar 2004 07:29:13 -0500 (EST)
Received: from www.gasbuggy.homeunix.net (gasbuggy [192.168.0.100])
	by homeunix.net (8.12.10+Sun/8.12.10) with SMTP id i2QCTCmH010297
	for <users@conserver.com>; Fri, 26 Mar 2004 07:29:12 -0500 (EST)
Received: from 192.85.47.2 (SquirrelMail authenticated user pete)
	by www.gasbuggy.homeunix.net with HTTP;
	Fri, 26 Mar 2004 07:29:12 -0500 (EST)
Message-ID: <32842.192.85.47.2.1080304152.squirrel@www.gasbuggy.homeunix.net>
Date: Fri, 26 Mar 2004 07:29:12 -0500 (EST)
From: "Pete Geenhuizen" <pgeenhuizen@carolina.rr.com>
To: users@conserver.com
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_1080304158-607-64"
X-Priority: 3
Importance: Normal
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Spam-Score: -2.593 () BAYES_00, HTML_MESSAGE, HTML_MIME_NO_HTML_TAG,
	MIME_HTML_ONLY, PRIORITY_NO_NAME
X-Scanned-By: MIMEDefang 2.39
Subject: Config/operation question
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2004 12:29:21 -0000

This is a multi-part message in MIME format...

------------=_1080304158-607-64
Content-Type: text/html;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Disposition: inline

<p>Just compiled conserver and am testing it for possible use, looks
promising thus far.  I do have a question about the
<strong>reinitcheck</strong> option, and perhaps I'm miss interpreting
it.</p><p>Reintcheck as best I can tell sets up a delay or frequency for
conserver to check the connection to a particular host, and if the
connection is broken it will then re-connect, is that correct?</p><p>I've
set the value to ten thinking it was seconds, but I believe that its
minutes according to the -O option, so I'll need to change that.  Either
way I don't see that it has any affect,providing that my assumption is
correct.</p><p>What I want to do/need is to be able to go to the terminal
concentrator and reset the port so that I can use the old fashioned way of
connecting to the console, and then when I'm done have conserver pick up
the console once again.</p><p>Is reinitcheck the way to do that or is
there another alternative, as it stand now as soon as I issue a port reset
conserver detects the disconnect and immediately re-connects.</p><p>Thanks
in advance for any insight or help that you could provide.</p><p
/><p>Pete<br />-- <br />&quot;Unencumbered by the thought process&quot;
<br />--1992-2000 Click and Clack presidential campaign slogan <br /><br
/></p>

------------=_1080304158-607-64--
From bryan@stansell.org Fri Mar 26 05:01:30 2004
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2QD1SG2000896
	for <users@conserver.com>; Fri, 26 Mar 2004 05:01:30 -0800 (PST)
Received: (from bryan@localhost)
	by underdog.stansell.org (8.12.11/8.12.11/Submit) id i2QD1RKM000895
	for users@conserver.com; Fri, 26 Mar 2004 05:01:27 -0800 (PST)
Date: Fri, 26 Mar 2004 05:01:27 -0800
From: Bryan Stansell <bryan@conserver.com>
To: users@conserver.com
Message-ID: <20040326130127.GO12935@underdog.stansell.org>
References: <32842.192.85.47.2.1080304152.squirrel@www.gasbuggy.homeunix.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=unknown-8bit
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <32842.192.85.47.2.1080304152.squirrel@www.gasbuggy.homeunix.net>
User-Agent: Mutt/1.4.2.1i
X-Scanned-By: MIMEDefang 2.39
Subject: Re: Config/operation question
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2004 13:01:32 -0000

On Fri, Mar 26, 2004 at 07:29:12AM -0500, Pete Geenhuizen wrote:
>    Reintcheck as best I can tell sets up a delay or frequency for
>    conserver to check the connection to a particular host, and if the
>    connection is broken it will then re-connect, is that correct?

basically.  any and all consoles that are marked "down" (as in, not
connected) will attempt a connection every X minutes.

>    I've set the value to ten thinking it was seconds, but I believe
>    that its minutes according to the -O option, so I'll need to change
>    that. Either way I don't see that it has any affect,providing that
>    my assumption is correct.

yeah, it's really like the -O option, so minutes.  the conserver.cf
manpage is wrong...it'll say minutes instead of seconds in the next
release (which matches the -O docs).  sorry about that.

>    What I want to do/need is to be able to go to the terminal
>    concentrator and reset the port so that I can use the old fashioned
>    way of connecting to the console, and then when I'm done have
>    conserver pick up the console once again.
> 
>    Is reinitcheck the way to do that or is there another alternative, as
>    it stand now as soon as I issue a port reset conserver detects the
>    disconnect and immediately re-connects.

what you're seeing is expected...the "problem" is there are multiple
ways to tweak things and you've only pulled on lever #1.  here are the
other things to look at:

 1. autoreinit option
    this controls the automatic attempt to bring up the console (which
    is what you're seeing).  if the initial attempt doesn't succeed,
    it'll reattempt every minute thereafter.  this automatic behavior
    occurs only when a console connection is broken - not when a console
    has been taken down by a user (^Ecd).

 2. reinitcheck option
    this is a timer that goes off every X minutes and finds all the
    consoles that are down (from a broken connection or user command)
    and tries to bring it back up.

 3. reinitoncc option
    this will cause a connection attempt for a downed console (because
    of a broken connection or user command) when a client connects.
    this is off by default, so you may not need to worry about it.

so, if you enable reinitcheck and autoreinit (your case), you'll have
two behaviors happening, depending on how a console goes down.  if the
connection is broken, the autoreinit option will trigger an automatic
reconnection, with an attempt every minute as long as it fails.  the
reinitcheck timer will also be going off every X minutes and trying to
bring up the console (and any other consoles that are down).  if,
however, you connect to the console and do a '^Ecd', the autoreinit
option doesn't apply and you'll have anywhere from zero seconds to X
minutes before the reinitcheck timer goes off and attempts to bring the
console back up.  as long as you tie up the console in some other way,
conserver will reattempt that connection every X minutes, like you
expected.

so, as you can see, there are two key levers and one other interesting
one.  with that, you have 4 very interesting (and 4 more
semi-interesting) ways of configuring conserver regarding automatic
console initializations.  and i totally left out the 'ondemand'
option...but that doesn't really help you.  ;-)

hopefully with all those levers, you'll find a behavior you like.

Bryan
From c102mr@uibk.ac.at Fri Mar 26 05:49:46 2004
Received: from smtp.uibk.ac.at (lmr1.uibk.ac.at [138.232.1.142])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2QDnfMB002520
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <users@conserver.com>; Fri, 26 Mar 2004 05:49:43 -0800 (PST)
Received: from red-c102.uibk.ac.at (red-c102.uibk.ac.at [138.232.3.93])
	by smtp.uibk.ac.at (8.12.10/8.12.10/F1) with ESMTP id i2QDnd8J027397
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <users@conserver.com>; Fri, 26 Mar 2004 14:49:40 +0100
Date: Fri, 26 Mar 2004 14:49:34 +0100 (CET)
From: Michael Redinger <Michael.Redinger@uibk.ac.at>
To: users@conserver.com
Message-ID: <Pine.LNX.4.44.0403261429260.3732-100000@red-c102.uibk.ac.at>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: -4.901 () BAYES_00
X-Scanned-By: MIMEDefang 2.39
X-Scanned-By: MIMEDefang 2.39 at uibk.ac.at
Subject: CRLF logging
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2004 13:49:48 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hello,

when testing conserver I found that the logfiles contain CRLF, LF and CR
line terminators.
Most lines are ended with CRLF (but I also saw lines with only LF).
Also, there is often a CR right after the timestamp.
See the example below (note the "^M"s).

My configuration is rather simple, it is very similar to average.cf
(except for setting timestamp to "1lab").

Both the conserver and the host of the serial console are running
Red Hat Enterprise Linux 3.0.

Who is to blame, conserver or the Linux server system?
I remember seeing something like this in Cyclades TS logs, so I suppose
it is not very unusual.
Is there any way to prevent this?

Thanks,
Michael


[Fri Mar 26 11:56:19 2004]^M        aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs
[Fri Mar 26 11:56:19 2004]^M
[Fri Mar 26 11:56:19 2004]^Mscsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
[Fri Mar 26 11:56:19 2004]^M        <Adaptec aic7880 Ultra SCSI adapter>


[Fri Mar 26 11:57:10 2004]Starting Red Hat Network Daemon: [  OK  ]^M^M
[Fri Mar 26 11:57:11 2004]Starting mdmpd: [  OK  ]^M^M
[Fri Mar 26 11:57:12 2004]^M
[Fri Mar 26 11:57:12 2004]Red Hat Enterprise Linux AS release 3 (Taroon Update 1)^M
[Fri Mar 26 11:57:12 2004]Kernel 2.4.21-9.0.1.ELsmp on an i686^M
[Fri Mar 26 11:57:12 2004]^M
[Fri Mar 26 11:57:12 2004]XXX.uibk.ac.at login: ^M
[Fri Mar 26 12:00:05 2004]Red Hat Enterprise Linux AS release 3 (Taroon Update 1)^M
[Fri Mar 26 12:00:05 2004]Kernel 2.4.21-9.0.1.ELsmp on an i686^M
[Fri Mar 26 12:00:05 2004]^M
[Fri Mar 26 12:00:05 2004]XXX.uibk.ac.at login: ^M


- -- 
Michael Redinger
Zentraler Informatikdienst (Computer Centre)
Universitaet Innsbruck                  
Technikerstrasse 13                     Tel.: ++43 512 507 2335
6020 Innsbruck                          Fax.: ++43 512 507 2944
Austria					Mail: Michael.Redinger@uibk.ac.at
BB98 D2FE 0F2C 2658 3780  3CB1 0FD7 A9D9 65C2 C11D
http://www.uibk.ac.at/~c102mr/mred-pubkey.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAZDTzD9ep2WXCwR0RAumcAJ9T9a0lg6QwS5rZpAVPXozWWZfVsACdEEmW
E6kVlFkDbL8kYzuTSTSSPo4=
=3PQS
-----END PGP SIGNATURE-----


From bryan@stansell.org Fri Mar 26 06:14:44 2004
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2QEEhMl003392
	for <users@conserver.com>; Fri, 26 Mar 2004 06:14:44 -0800 (PST)
Received: (from bryan@localhost)
	by underdog.stansell.org (8.12.11/8.12.11/Submit) id i2QEEhtM003391
	for users@conserver.com; Fri, 26 Mar 2004 06:14:43 -0800 (PST)
Date: Fri, 26 Mar 2004 06:14:43 -0800
From: Bryan Stansell <bryan@conserver.com>
To: users@conserver.com
Message-ID: <20040326141443.GP12935@underdog.stansell.org>
References: <Pine.LNX.4.44.0403261429260.3732-100000@red-c102.uibk.ac.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0403261429260.3732-100000@red-c102.uibk.ac.at>
User-Agent: Mutt/1.4.2.1i
X-Scanned-By: MIMEDefang 2.39
Subject: Re: CRLF logging
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2004 14:14:46 -0000

On Fri, Mar 26, 2004 at 02:49:34PM +0100, Michael Redinger wrote:
> when testing conserver I found that the logfiles contain CRLF, LF and CR
> line terminators.
> Most lines are ended with CRLF (but I also saw lines with only LF).
> Also, there is often a CR right after the timestamp.
> See the example below (note the "^M"s).

that's pretty wild.  not surprising, really, but interesting.  the
characters spit out by various pcs when booting is fun to see.

> Who is to blame, conserver or the Linux server system?

the server.  unless there's a bug, conserver "blindly" takes all the
data it gets from the console and writes it to the log file.  if it
weren't for the timestamping, it would be a byte-for-byte replica of
everything it receives.  since you have timestamping, the extra info is
also written.  the only interpretation conserver is doing in your case
is looking for a LF, so it can insert the timestamp.  but, again, any
binary data, CR, etc is coming from the console.

> I remember seeing something like this in Cyclades TS logs, so I suppose
> it is not very unusual.

extactly.

> Is there any way to prevent this?

not from withing conserver.  if conserver were to just strip all CR
characters, it might drop things that are actually important.  if it
weren't for the 7-bit mode (-7 option), i'd say that all the data is
always left exactly as it was recieved (with the exception of inserts
like timestamp).  the 7-bit mode is probably useless these days (and if
you're seeing bad high-bit data, you've probably got a low-level serial
configuration issue) and i'd like to get rid of it so i can say that
conserver always logs exactly what it sees coming from the console 100%
of the time.  that's a basic philosophy i'd like to maintain (hence my
desire to drop the -7 stuff).

does any of that help?

Bryan
From pgeenhuizen@carolina.rr.com Mon Mar 29 03:00:29 2004
Received: from ms-smtp-03-eri0.southeast.rr.com
	(ms-smtp-03-lbl.southeast.rr.com [24.25.9.102])
	by underdog.stansell.org (8.12.11/8.12.11) with ESMTP id i2TB0RBU007881
	for <users@conserver.com>; Mon, 29 Mar 2004 03:00:28 -0800 (PST)
Received: from homeunix.net (clt25-91-086.carolina.rr.com [24.25.91.86])
	by ms-smtp-03-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id
	i2TB0Os1022764
	for <users@conserver.com>; Mon, 29 Mar 2004 06:00:24 -0500 (EST)
Received: from gasbuggy.homeunix.net (gasbuggy [192.168.0.100])
	by homeunix.net (8.12.10+Sun/8.12.10) with SMTP id i2TB0NmH009089
	for <users@conserver.com>; Mon, 29 Mar 2004 06:00:23 -0500 (EST)
Received: from 192.168.0.2 (SquirrelMail authenticated user pete)
	by gasbuggy.homeunix.net with HTTP;
	Mon, 29 Mar 2004 06:00:23 -0500 (EST)
Message-ID: <2629.192.168.0.2.1080558023.squirrel@gasbuggy.homeunix.net>
In-Reply-To: <32842.192.85.47.2.1080304152.squirrel@www.gasbuggy.homeunix.net>
References: <32842.192.85.47.2.1080304152.squirrel@www.gasbuggy.homeunix.net>
Date: Mon, 29 Mar 2004 06:00:23 -0500 (EST)
From: "Pete Geenhuizen" <pgeenhuizen@carolina.rr.com>
To: users@conserver.com
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_1080558028-27966-76"
X-Priority: 3
Importance: Normal
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Spam-Score: -2.593 () BAYES_00, HTML_MESSAGE, HTML_MIME_NO_HTML_TAG,
	MIME_HTML_ONLY, PRIORITY_NO_NAME
X-Scanned-By: MIMEDefang 2.39
Subject: Re: Config/operation question
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: Conserver Users <users.conserver.com>
List-Unsubscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=unsubscribe>
List-Archive: <https://www.conserver.com/pipermail/users>
List-Post: <mailto:users@conserver.com>
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
X-List-Received-Date: Mon, 29 Mar 2004 11:00:31 -0000

This is a multi-part message in MIME format...

------------=_1080558028-27966-76
Content-Type: text/html;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Disposition: inline


Drat, I was hoping for something simple, oh well.<br />I'll try out your
suggestions to see which one will do what I want.<br /><br />Thx<br
/>Pete<br />-- <br />&quot;Unencumbered by the thought process&quot;<br
/>--1992-2000 Click and Clack presidential campaign slogan<br /><br />Pete
Geenhuizen said:<br />&gt; <p>Just compiled conserver and am testing it
for possible use, looks<br />&gt; promising thus far.  I do have a
question about the<br />&gt; <strong>reinitcheck</strong> option, and
perhaps I'm miss interpreting<br />&gt; it.</p><p>Reintcheck as best I can
tell sets up a delay or frequency for<br />&gt; conserver to check the
connection to a particular host, and if the<br />&gt; connection is broken
it will then re-connect, is that correct?</p><p>I've<br />&gt; set the
value to ten thinking it was seconds, but I believe that its<br />&gt;
minutes according to the -O option, so I'll need to change that. 
Either<br />&gt; way I don't see that it has any affect,providing that my
assumption is<br />&gt; correct.</p><p>What I want to do/need is to be
able to go to the terminal<br />&gt; concentrator and reset the port so
that I can use the old fashioned way of<br />&gt; connecting to the
console, and then when I'm done have conserver pick up<br />&gt; the
console once again.</p><p>Is reinitcheck the way to do that or is<br
/>&gt; there another alternative, as it stand now as soon as I issue a
port reset<br />&gt; conserver detects the disconnect and immediately
re-connects.</p><p>Thanks<br />&gt; in advance for any insight or help
that you could provide.</p><p =""><br />&gt; /&gt;</p><p>Pete<br />-- <br
/>&quot;Unencumbered by the thought process&quot;<br />&gt; <br
/>--1992-2000 Click and Clack presidential campaign slogan <br /><br =""
/><br />&gt; /&gt;</p><br />&gt;
_______________________________________________<br />&gt; users mailing
list<br />&gt; users@conserver.com<br />&gt;
https://www.conserver.com/mailman/listinfo/users<br />&gt; <br />

------------=_1080558028-27966-76--