From bjaques@cablecar.net Mon Apr  8 12:33:35 2002
Received: from cablecar.net (adsl-63-201-252-67.dsl.snfc21.pacbell.net [63.201.252.67])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g38JXZ2S018207
	for <users@conserver.com>; Mon, 8 Apr 2002 12:33:35 -0700 (PDT)
Received: from [63.204.150.209] (account <bjaques@cablecar.net>)
  by cablecar.net (CommuniGate Pro WebUser 3.4.7)
  with HTTP id 570285 for <users@conserver.com>; Mon, 08 Apr 2002 12:33:34 -0700
From: "Robert R. Jaques" <bjaques@cablecar.net>
Subject: help with configuring conserver
To: users@conserver.com
X-Mailer: CommuniGate Pro Web Mailer v.3.4.7
Date: Mon, 08 Apr 2002 12:33:34 -0700
Message-ID: <web-570285@cablecar.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

 I have a magma 4 port pci serial card in a Sun netra
running solaris 8 and have installed conserver
 

I have the  ports configured


tty0:/dev/tty0:9600p:&:

if I type console -u I see 
tty0              down <none>

I am trying to connect cisco equipment, pixs 2900 and 6000
switches. I am using ca cisco cable I always use on my lap
top

when i type console tty0
and loging

it says console: tty0 is down

I cannot seem to start it or get a connection even with 
a Ctrl E c a

in admin tools tty0 shows up as
port 0
portmontor ttymon0
service tage tty0
terminal hardwired.

any help would be appreciated..


   


From sebby@atalanta.ctd.anl.gov Mon Apr  8 16:56:49 2002
Received: from atalanta.ctd.anl.gov (atalanta.ctd.anl.gov [146.137.64.60])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g38Num2S020279
	for <users@conserver.com>; Mon, 8 Apr 2002 16:56:48 -0700 (PDT)
Received: (from sebby@localhost)
      by atalanta.ctd.anl.gov (8.9.1a/8.9.1) id SAA03149
      for users@conserver.com; Mon, 8 Apr 2002 18:56:42 -0500 (CDT)
Date: Mon, 8 Apr 2002 18:56:42 -0500
From: Brian Sebby <sebby@anl.gov>
To: users@conserver.com
Subject: Conserver 7.2.1 not checking passwords
Message-ID: <20020408185642.A2945@atalanta.ctd.anl.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

I compiled conserver 7.2.1 today on our console server, and ran into a
problem.  While the software compiled fine, and allowed me to talk to the
consoles with no problem, it no longer seems to be checking the password
of the user using it.  I haven't changed the conserver.passwd file that I've
been using for a while, and all of its entries are of the form:

<username>:*passwd*:any

I used the following options to confire when I compiled it:

/configure --prefix=/usr/local --with-master=<our console server> --sysconfdir=/etc --with-logfile=/home/console.logs/conserver

One thing that I noticed during the configuration process were the following
lines:

checking for crypt.h... yes
checking for library containing crypt... none required

I tried explicitly telling it to use -lcrypt by trying to use the configure
option --with-PACKAGE=crypt, but that had no effect.  I also tried adding
the string -lcrypt to the LIBS line in the conserver and console Makefiles.
That didn't have any effect either.  I even tried making the conserver.passwd
files readable by any user, to no effect.

The system I am building it on is an UltraSparc 5 with an Aurora Technologies
Aries serial port expander.  As I said, the console part of it works fine -
I just want to make sure that it checks passwords.  If anyone has an idea
about what could be wrong, please let me know.


Thanks,

Brian

-- 
Brian Sebby  (sebby@anl.gov)  |  Distributed Computing Administration
Phone: +1 630.252.9935        |  Electronics and Computing Technologies
Fax:   +1 630.252.9689        |  Argonne National Laboratory

From anders@totem.fix.no Tue Apr  9 05:45:48 2002
Received: from totem.fix.no (postfix@totem.fix.no [80.91.32.29])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g39Cjl2S029769
	for <users@conserver.com>; Tue, 9 Apr 2002 05:45:48 -0700 (PDT)
Received: by totem.fix.no (Postfix, from userid 1000)
	id C48A82031E; Tue,  9 Apr 2002 14:46:22 +0200 (CEST)
Date: Tue, 9 Apr 2002 14:46:22 +0200
From: Anders Nordby <anders@fix.no>
To: users@conserver.com
Subject: Telnet BRK, logging, conserver rocks, etc.
Message-ID: <20020409124622.GA12004@totem.fix.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
X-message-flag: Outlook : A program to spread viri, but it can do mail too.
X-PGP-Key: http://anders.fix.no/pgp/
X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD  19C5 D12A BC9F 0083 5956
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

Hello,

Just wanted to say thanks for making/maintaining wonderful software.
I went through some problems to be able to SEND break signal to some Sun
machines through conserver + piped telnet + a Cisco 2511 access server,
but finally solved it. Thought I'd share my solution. In conserver.cf,
put:

BREAK3=^]send brk\n

The ^] needs to be HEX 0A (in vi: control + alt gr + 9 on my Sun). Of
course, one can always send control + alt gr + 9 on the keyboard
directly and type send brk, but I prefer to have everything set up to be
available through ^ec<foo> which is described by the help that is showed
when running console.

I also need to log some more stuff (like which users attaches/deattaches
from consoles, the time they do this (when attaching/deattaching)), but
I suppose I'll figure that out. If anyone has some patches/tips in
regards to logging more than the default, let me know.

Regards,

-- 
Anders.

From todd@stansell.org Tue Apr  9 15:20:38 2002
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g39MKb2S004213;
	Tue, 9 Apr 2002 15:20:37 -0700 (PDT)
Received: (from todd@localhost)
	by underdog.stansell.org (8.12.2/8.12.2/Submit) id g39MKbpZ004212;
	Tue, 9 Apr 2002 15:20:37 -0700 (PDT)
Date: Tue, 9 Apr 2002 15:20:37 -0700
From: Todd Stansell <todd@stansell.org>
To: Anders Nordby <anders@fix.no>
Cc: users@conserver.com
Subject: Re: Telnet BRK, logging, conserver rocks, etc.
Message-ID: <20020409152037.N1212@underdog.stansell.org>
References: <20020409124622.GA12004@totem.fix.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20020409124622.GA12004@totem.fix.no>; from anders@fix.no on Tue, Apr 09, 2002 at 02:46:22PM +0200
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

On Tue, Apr 09, 2002 at 02:46:22PM +0200, Anders Nordby wrote:
> I also need to log some more stuff (like which users attaches/deattaches
> from consoles, the time they do this (when attaching/deattaching)), but
> I suppose I'll figure that out. If anyone has some patches/tips in
> regards to logging more than the default, let me know.

Add the "a" option to TIMESTAMP in conserver.cf.  Check out the
conserver.cf manpage for the explaination.

Todd

From sebby@atalanta.ctd.anl.gov Tue Apr  9 16:30:43 2002
Received: from atalanta.ctd.anl.gov (atalanta.ctd.anl.gov [146.137.64.60])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g39NUg2S004744
	for <users@conserver.com>; Tue, 9 Apr 2002 16:30:42 -0700 (PDT)
Received: (from sebby@localhost)
      by atalanta.ctd.anl.gov (8.9.1a/8.9.1) id SAA08236
      for users@conserver.com; Tue, 9 Apr 2002 18:30:37 -0500 (CDT)
Date: Tue, 9 Apr 2002 18:30:37 -0500
From: Brian Sebby <sebby@anl.gov>
To: users@conserver.com
Subject: Followup: Conserver 7.2.1 not checking passwords
Message-ID: <20020409183037.A7973@atalanta.ctd.anl.gov>
References: <20020408185642.A2945@atalanta.ctd.anl.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20020408185642.A2945@atalanta.ctd.anl.gov>; from sebby@anl.gov on Mon, Apr 08, 2002 at 06:56:42PM -0500
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

On Mon, Apr 08, 2002 at 06:56:42PM -0500, Brian Sebby wrote:
> I compiled conserver 7.2.1 today on our console server, and ran into a
> problem.  While the software compiled fine, and allowed me to talk to the
> consoles with no problem, it no longer seems to be checking the password
> of the user using it.  I haven't changed the conserver.passwd file that I've
> been using for a while, and all of its entries are of the form:

I managed to solve my own problem.  I was reading through the archives of the
mailing list, and saw in a post by Scott Matott (thanks!) information about
"allowed" vs. "trusted" hosts in conserver.cf.  I discovered that my console
server had been set to "trusted" and not "allowed".  Now, what is interesting
is that it has been that way for quite a while, but apparently the version
that we had been using (6.16) still asked for passwords on trusted hosts.
The software is working great now, and thanks again to Bryan and the rest of
the developers for creating such a useful program.  (It was nice to be able
to just do a kill -HUP to reread the config file after I edited it. :) )


Brian

-- 
Brian Sebby  (sebby@anl.gov)  |  Distributed Computing Administration
Phone: +1 630.252.9935        |  Electronics and Computing Technologies
Fax:   +1 630.252.9689        |  Argonne National Laboratory

From bryan@conserver.com Wed Apr 10 15:19:57 2002
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g3AMJv2S018697
	for <users@conserver.com>; Wed, 10 Apr 2002 15:19:57 -0700 (PDT)
Received: (from nobody@localhost)
	by underdog.stansell.org (8.12.2/8.12.2/Submit) id g3AMJvto018696
	for users@conserver.com; Wed, 10 Apr 2002 15:19:57 -0700 (PDT)
X-Authentication-Warning: underdog.stansell.org: nobody set sender to bryan@conserver.com using -f
To: users@conserver.com
Subject: Re: Telnet BRK, logging, conserver rocks, etc.
Message-ID: <1018477196.3cb4ba8ceec04@www.stansell.org>
Date: Wed, 10 Apr 2002 15:19:56 -0700 (PDT)
From: bryan@conserver.com
References: <20020409124622.GA12004@totem.fix.no>
In-Reply-To: <20020409124622.GA12004@totem.fix.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.7
X-Originating-IP: 202.37.68.123
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

hi there,

a quick note and question.  first, instead of having to type an escape, you 
should be able to use

BREAK3=\esend break\n

if i remember right, anyway.  the man page should say for sure (i can't check 
it right now), but i'm pretty sure \e will translate to an escape.

as for the question, are you using something like:

con:|telnet cisco 2002:::

or something like

con:!cisco:2002::

in your conserver.cf file?  if you're using the first, conserver is going to 
fork off a telnet process (and associtate a pseudo-tty for each telnet) to 
communicate with each console.  in the second form, conserver creates a tcp 
connection to the port just like telnet will.  that will allow you to use the 
^ecl1 sequence to send a break.  it's still good for folks to know how to set 
up the '\esend brk\n' thing ('cause, who knows, some cases may need it), but 
it's a lot less of an impact on your system if conserver can create the sockets 
itself.

anyway, the conserver.cf manpage should explain how to set this stuff up.  just 
wanted to make folks aware of the system impact.

Bryan

Quoting Anders Nordby <anders@fix.no>:
> Hello,
> 
> Just wanted to say thanks for making/maintaining wonderful software.
> I went through some problems to be able to SEND break signal to some
> Sun
> machines through conserver + piped telnet + a Cisco 2511 access
> server,
> but finally solved it. Thought I'd share my solution. In conserver.cf,
> put:
> 
> BREAK3=^]send brk\n
> 
> The ^] needs to be HEX 0A (in vi: control + alt gr + 9 on my Sun). Of
> course, one can always send control + alt gr + 9 on the keyboard
> directly and type send brk, but I prefer to have everything set up to
> be
> available through ^ec<foo> which is described by the help that is
> showed
> when running console.

From bryan@conserver.com Wed Apr 10 15:28:21 2002
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g3AMSL2S018813
	for <users@conserver.com>; Wed, 10 Apr 2002 15:28:21 -0700 (PDT)
Received: (from nobody@localhost)
	by underdog.stansell.org (8.12.2/8.12.2/Submit) id g3AMSLEi018812
	for users@conserver.com; Wed, 10 Apr 2002 15:28:21 -0700 (PDT)
X-Authentication-Warning: underdog.stansell.org: nobody set sender to bryan@conserver.com using -f
To: users@conserver.com
Subject: Re: help with configuring conserver
Message-ID: <1018477701.3cb4bc8558347@www.stansell.org>
Date: Wed, 10 Apr 2002 15:28:21 -0700 (PDT)
From: bryan@conserver.com
References: <web-570285@cablecar.net>
In-Reply-To: <web-570285@cablecar.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.7
X-Originating-IP: 202.37.68.226
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

hi robert,

well, the best pointer i can give you is to try and use 'tip' or some other 
serial port access program to talk to the console before involving conserver.  
your setup looks correct.  a couple of questions:  are you running conserver as 
root (if not, do you have permission to open /dev/tty0) and are there other 
ports that you should be using for "dialing out" (which is effectively what 
you're doing...some systems use /dev/cua* instead of /dev/tty*, etc).  
hopefully the magma serial card folks have instructions for what devices to 
use, etc.  if /dev/tty0 is the right device and you have permission to open it, 
it could be that the cable is wrong for this purpose (laptops and suns have 
reverse pinouts, if i remember, so you may need a null-modem added to the mix).

in other cases, i follow the instructions of the serial port manufacturer (they 
usually have a step-by-step set of instructions for 'tip' or something), and 
then once that works, point conserver at the same point.  like i said, it looks 
like you're doing the right thing at the conserver level.

hope that helps a little.

Bryan

Quoting "Robert R. Jaques" <bjaques@cablecar.net>:
>  I have a magma 4 port pci serial card in a Sun netra
> running solaris 8 and have installed conserver
>  
> 
> I have the  ports configured
> 
> 
> tty0:/dev/tty0:9600p:&:
> 
> if I type console -u I see 
> tty0              down <none>
> 
> I am trying to connect cisco equipment, pixs 2900 and 6000
> switches. I am using ca cisco cable I always use on my lap
> top
> 
> when i type console tty0
> and loging
> 
> it says console: tty0 is down
> 
> I cannot seem to start it or get a connection even with 
> a Ctrl E c a
> 
> in admin tools tty0 shows up as
> port 0
> portmontor ttymon0
> service tage tty0
> terminal hardwired.
> 
> any help would be appreciated..

From woods@proven.weird.com Wed Apr 24 15:53:27 2002
Received: from most.weird.com (IDENT:x/sl8wXpP8ZHFeqEdW/g8uIVssMT76dfw3mplQ5VnzH0o+OeQ9ESDLOFGU+UObHejRVmlsDX48c@most.weird.com [204.92.254.2])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g3OMrQ2S017512
	for <users@conserver.com>; Wed, 24 Apr 2002 15:53:27 -0700 (PDT)
Received: from proven.weird.com([204.92.254.15]) (2660 bytes) by most.weird.com
	via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <woods@proven.weird.com>) 
	(ident <[hzrVXYuuwUkCE38BCWgl9zaL8SNzMdYtZVHRMfWsX6sKPVQw9E+krHK4G/GhI7nYTKpOh/weM2LTjgDIEx/IAA==]> using rfc1413)
	id <m170Vdc-000g6PC@most.weird.com>
	for <users@conserver.com>; Wed, 24 Apr 2002 18:53:24 -0400 (EDT)
	(Smail-3.2.0.115-Pre 2001-Aug-6 #2 built 2002-Apr-22)
Received: by proven.weird.com (Postfix, from userid 1000)
	id 2ACE4AC; Wed, 24 Apr 2002 18:53:19 -0400 (EDT)
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: woods@weird.com (Greg A. Woods)
To: users@conserver.com (ConServer Users Mailing List)
Subject: some wish-list items for conserver....
X-Mailer: VM 7.03 under Emacs 21.2.1
Reply-To: users@conserver.com (ConServer Users Mailing List)
Organization: Planix, Inc.; Toronto, Ontario; Canada
Message-Id: <20020424225319.2ACE4AC@proven.weird.com>
Date: Wed, 24 Apr 2002 18:53:19 -0400 (EDT)
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

Here are some ideas for the TODO list!  :-)

I'm going to actually try to work on the first one -- it's absolutely
critical in my environment where every connection to the terminal server
requires an access password to be entered, and so if conserver restarts
for any reason it has to enter the password before any output from the
ports can be logged.  Right now I have to manually connect to every
console and enter the password by hand (er, cut&paste :-), which of
course is far less than ideal....

Index: TODO
===================================================================
RCS file: /cvs/misc/conserver/TODO,v
retrieving revision 1.1.1.2
diff -c -r1.1.1.2 TODO
*** TODO	16 Mar 2002 22:23:57 -0000	1.1.1.2
--- TODO	16 Mar 2002 22:25:33 -0000
***************
*** 98,103 ****
--- 98,112 ----
  - support 2 stop bits (as well as other stty-type options in console
    definitions) : Kelly Setzer <setzer@placemark.com>
  
+ - ability to configure strings to be sent to a console whenever it is
+   (re)opened (eg. a termserver login) : Greg A. Woods <woods@planix.com>
+ 
+ - ability to configure strings to be sent to a console periodically
+   : Greg A. Woods <woods@planix.com>
+ 
+ - show attach/detach events to/of spy console clients
+   : Greg A. Woods <woods@planix.com>
+ 
  #
  #  $Id: TODO,v 1.22 2002-03-11 18:11:48-08 bryan Exp $
  #

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>

From woods@proven.weird.com Wed Apr 24 17:12:54 2002
Received: from most.weird.com (IDENT:JSORUS3Bxzd58iDF65/RCwUIbiRAwZM2p1C99zVcIZZ70+mvPV9P0KseLnWXuTjKB73UdC2Nh8o@most.weird.com [204.92.254.2])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g3P0Cr2S018130
	for <users@conserver.com>; Wed, 24 Apr 2002 17:12:53 -0700 (PDT)
Received: from proven.weird.com([204.92.254.15]) (4938 bytes) by most.weird.com
	via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <woods@proven.weird.com>) 
	(ident <[jK8RC8f4o6as84Hayh45RpoSN2c6UzsFk2pSI0KmGzIlsbNF9U9Z6z3A9132NMUGnGXOOXJd0jqgQQx4PdukRA==]> using rfc1413)
	id <m170WsU-000g6PC@most.weird.com>
	for <users@conserver.com>; Wed, 24 Apr 2002 20:12:50 -0400 (EDT)
	(Smail-3.2.0.115-Pre 2001-Aug-6 #2 built 2002-Apr-22)
Received: by proven.weird.com (Postfix, from userid 1000)
	id A98FDAC; Wed, 24 Apr 2002 20:12:49 -0400 (EDT)
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: woods@weird.com (Greg A. Woods)
To: users@conserver.com (ConServer Users Mailing List)
Subject: signal handling bugs continue in 7.2.0 on *BSD
X-Mailer: VM 7.03 under Emacs 21.2.1
Reply-To: users@conserver.com (ConServer Users Mailing List)
Organization: Planix, Inc.; Toronto, Ontario; Canada
Message-Id: <20020425001249.A98FDAC@proven.weird.com>
Date: Wed, 24 Apr 2002 20:12:49 -0400 (EDT)
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

I can still reproduce the problem with feeding stdin to the "console"
command causing conserver to crash.  However in 7.2.0 it now only
happens when you have to use 'console -F'.  (maybe that's the only way
it failed in 7.1.3 too -- I can't remember if I only tested with '-F'
then too or not, though I may very well have)

This is with conserver-7.2.0, on NetBSD-1.5W/sparc.

This stdin trick works fine without '-F' though ('very' is a
not-so-important conserver host to which a caller-ID box is attached and
it behaves like a modem with an AT command syntax):

	$ printf "at\r\n" | console -M very callerid
	[Enter `^Ec?' for help]
	$ tail /var/log/consoles/callerid
	[-- woods@very.weird.com attached -- Wed Apr 24 19:17:17 2002]
	[-- woods@very.weird.com detached -- Wed Apr 24 19:17:17 2002]
	at
	[Wed Apr 24 19:17:18 2002]OK
	[Wed Apr 24 19:17:18 2002]

However with another console session attached an attempt to do the above
with 'console -F' causes the following:

conserver (163): conserver(165): signal(13), restarted [Wed Apr 24 19:10:05 2002]

Note that 'console -f' does work though:

	$ printf "at\r\n" | console -f -M very callerid
	[Enter `^Ec?' for help]
	$ tail /var/log/consoles/callerid               
	[-- woods@very.weird.com bumped woods@becoming.weird.com -- Wed Apr 24 19:20:20 2002]
	[-- woods@very.weird.com detached -- Wed Apr 24 19:20:21 2002]
	[-- woods@becoming.weird.com attached -- Wed Apr 24 19:20:21 2002]
	[Wed Apr 24 19:20:21 2002]at
	[Wed Apr 24 19:20:21 2002]OK
	[Wed Apr 24 19:20:21 2002]

With a delay in the right place I don't even have to read the log file
to see the results -- they appear on stdout as expected:

	$ (printf "at\r\n"; sleep 5) | console -f -M very callerid
	[Enter `^Ec?' for help]
	[bumped woods@becoming.weird.com]
	
	at
	OK
	
	$ 

What's interesting is that 'console -F' works fine with the delay:

	$ (printf "at\r\n"; sleep 5) | console -F -M very callerid 
	
	[Enter `^Ec?' for help]
	[bumped woods@becoming.weird.com]
	[replay]
	[Wed Apr 24 19:19:29 2002]at
	[Wed Apr 24 19:19:29 2002]OK
	[Wed Apr 24 19:19:29 2002]
	[-- woods@becoming.weird.com attached -- Wed Apr 24 19:20:08 2002]
	[Wed Apr 24 19:20:10 2002]at 
	[Wed Apr 24 19:20:13 2002]OK
	[-- woods@very.weird.com bumped woods@becoming.weird.com -- Wed Apr 24 19:20:20 2002]
	[-- woods@very.weird.com detached -- Wed Apr 24 19:20:21 2002]
	[-- woods@becoming.weird.com attached -- Wed Apr 24 19:20:21 2002]
	[Wed Apr 24 19:20:21 2002]at
	[Wed Apr 24 19:20:21 2002]OK
	[Wed Apr 24 19:20:21 2002]
	[-- woods@very.weird.com bumped woods@becoming.weird.com -- Wed Apr 24 19:27:30 2002]
	[Wed Apr 24 19:27:30 2002]at
	[Wed Apr 24 19:27:31 2002]OK
	[Wed Apr 24 19:27:31 2002]
	[-- woods@very.weird.com detached -- Wed Apr 24 19:27:35 2002]
	[-- woods@becoming.weird.com attached -- Wed Apr 24 19:27:35 2002]
	[-- woods@very.weird.com bumped woods@becoming.weird.com -- Wed Apr 24 19:28:29 2002]
	at
	OK
	
	$ 

Note also that 'console -F' doesn't work properly at all if no other
session is attached and there's no delay before stdin is closed.  The
log shows the input from the client, but no output in response from the
port -- it's as if the input from the client never makes it out the
port even though it's logged....

Don't ask me why I was trying 'console -F' when I don't really need the
replay action -- probably just out of habit! :-)

At least now I can begin to write Cricket and NUT-UPS support for my UPS
units!  I think for now I'll parse the log file for now instead of
delaying stdin and reading stdin -- that way I can just run a simple
cron job to send the commands to the UPS'....

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>

From woods@proven.weird.com Wed Apr 24 18:27:03 2002
Received: from most.weird.com (IDENT:7O2/glETXHy1c93ZuDRTAbr2reE6HiXyq3KY48g9kMbLRJrEJVuVcO0tyJz3M3VqfGXwxXNMDzE@mail.weird.com [204.92.254.2])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g3P1R22S018701
	for <users@conserver.com>; Wed, 24 Apr 2002 18:27:03 -0700 (PDT)
Received: from proven.weird.com([204.92.254.15]) (9538 bytes) by most.weird.com
	via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <woods@proven.weird.com>) 
	(ident <[wu0Sb/whpq9kyy8trMe4Xi/xKFerhByUHqBaJNhiWJWrtUguHcLaiKebNIC6jt2jb04Dd7VESKRpLm9W1feFtQ==]> using rfc1413)
	id <m170Y2H-000g6PC@most.weird.com>
	for <users@conserver.com>; Wed, 24 Apr 2002 21:27:01 -0400 (EDT)
	(Smail-3.2.0.115-Pre 2001-Aug-6 #2 built 2002-Apr-22)
Received: by proven.weird.com (Postfix, from userid 1000)
	id BD8FEAC; Wed, 24 Apr 2002 21:26:59 -0400 (EDT)
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: woods@weird.com (Greg A. Woods)
To: users@conserver.com (ConServer Users Mailing List)
Subject: minor fixes of conserver.cf.man and 'n'one for partity matching
X-Mailer: VM 7.03 under Emacs 21.2.1
Reply-To: users@conserver.com (ConServer Users Mailing List)
Organization: Planix, Inc.; Toronto, Ontario; Canada
Message-Id: <20020425012659.BD8FEAC@proven.weird.com>
Date: Wed, 24 Apr 2002 21:26:59 -0400 (EDT)
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

The following patch adds 'n' (in addition to 'p') for "no parity".  This
is the traditional de facto standard abbreviation (eg. as in "8N1").

Minor improvements are also made to conserver.cf.man (in addition to
documenting this new parity flag).

(speaking of which, support for an optional stop-bits number following
the parity would probably be nice to have too)

Index: conserver/consent.c
===================================================================
RCS file: /cvs/misc/conserver/conserver/consent.c,v
retrieving revision 1.1.1.3
diff -c -r1.1.1.3 consent.c
*** conserver/consent.c	24 Apr 2002 21:42:00 -0000	1.1.1.3
--- conserver/consent.c	25 Apr 2002 00:47:53 -0000
***************
*** 124,133 ****
      ,				/* even                 */
      {'m', PARENB | CS7 | PARODD | PAREXT, 0}
      ,				/* mark                 */
      {'o', PARENB | CS7 | PARODD, 0}
      ,				/* odd                  */
      {'p', CS8, 0}
!     ,				/* pass 8 bits, no parity */
      {'s', PARENB | CS7 | PAREXT, 0}
      ,				/* space                */
  #else				/* ! HAVE_TERMIOS_H */
--- 124,135 ----
      ,				/* even                 */
      {'m', PARENB | CS7 | PARODD | PAREXT, 0}
      ,				/* mark                 */
+     {'n', CS8, 0}
+     ,				/* pass 8 bits, no parity */
      {'o', PARENB | CS7 | PARODD, 0}
      ,				/* odd                  */
      {'p', CS8, 0}
!     ,				/* pass 8 bits, no parity, old form */
      {'s', PARENB | CS7 | PAREXT, 0}
      ,				/* space                */
  #else				/* ! HAVE_TERMIOS_H */
***************
*** 139,144 ****
--- 141,148 ----
      ,				/* odd                                  */
  # if defined(PASS8)
      {'p', PASS8, EVENP | ODDP}
+     ,				/* pass 8 bits, no parity, old form     */
+     {'n', PASS8, EVENP | ODDP}
      ,				/* pass 8 bits, no parity               */
  # endif
      {'s', 0, EVENP | ODDP}	/* space                                */
Index: conserver.cf/conserver.cf.man
===================================================================
RCS file: /cvs/misc/conserver/conserver.cf/conserver.cf.man,v
retrieving revision 1.1.1.3
diff -c -r1.1.1.3 conserver.cf.man
*** conserver.cf/conserver.cf.man	24 Apr 2002 21:41:59 -0000	1.1.1.3
--- conserver.cf/conserver.cf.man	25 Apr 2002 01:16:20 -0000
***************
*** 4,24 ****
  .SH NAME
  conserver.cf \- console configuration file for conserver(8)
  .SH SYNOPSIS
- .br
  .BI \s-1LOGDIR\s0= logdirectory
! .br
  .BI \s-1TIMESTAMP\s0= timestamp-spec
! .br
  .BI \s-1BREAK\s0\fIn\fP= break-spec
! .br
  \fIname\fP:\fIdevice\fP[@\fIconserver\fP]:\fIbaud\fP:\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP
! .br
  \fIname\fP:!\fItermserver\fP[@\fIconserver\fP]:\fIport\fP:\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP
! .br
  \fIname\fP:|\fIcommand\fP[@\fIconserver\fP]::\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP
! .br
  \fB%%\fP
! .br
  \fIaccess\fP: \fIhosts\fP
  .SH DESCRIPTION
  .B Conserver.cf
--- 4,23 ----
  .SH NAME
  conserver.cf \- console configuration file for conserver(8)
  .SH SYNOPSIS
  .BI \s-1LOGDIR\s0= logdirectory
! .PP
  .BI \s-1TIMESTAMP\s0= timestamp-spec
! .PP
  .BI \s-1BREAK\s0\fIn\fP= break-spec
! .PP
  \fIname\fP:\fIdevice\fP[@\fIconserver\fP]:\fIbaud\fP:\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP
! .PP
  \fIname\fP:!\fItermserver\fP[@\fIconserver\fP]:\fIport\fP:\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP
! .PP
  \fIname\fP:|\fIcommand\fP[@\fIconserver\fP]::\fIlogfile\fP:\fItimestamp-spec\fP:\fIbreak\fP
! .PP
  \fB%%\fP
! .PP
  \fIaccess\fP: \fIhosts\fP
  .SH DESCRIPTION
  .B Conserver.cf
***************
*** 32,53 ****
  beginning with whitespace are considered continuations of the
  previous line.  This allows you to span one logical line over
  many physical lines and insert comments wherever appropriate.
  .PP
! The first section of the file has logical lines that are separated into
! five colon-separated fields.  Leading and trailing white space in each
! field is ignored.
  .TP
  .I name
  the unique name by which this connection is referred to
  when using the \fBconsole\fP program.
  This is typically the name of the host whose console is being monitored.
  .TP
  .I device
! the full path name of the device for this line.
! The \fIbaud\fP rate is the speed and parity for this console.
! Speed may be given as an integer,
! parity only requires the first letter of any of: even, odd, mark, space.
! For no parity, use the character `p'.
  .TP
  .BI ! termserver
  the hostname of the terminal server to connect to.
--- 31,53 ----
  beginning with whitespace are considered continuations of the
  previous line.  This allows you to span one logical line over
  many physical lines and insert comments wherever appropriate.
+ .SS "Console Specifications"
+ The first section of the file consists of lines either specifying the
+ details for a given console, or giving default setting for the following
+ group of console specifications.
  .PP
! Console specification lines are separated into five colon-separated
! fields.  Leading and trailing white space in each field is ignored.
  .TP
  .I name
  the unique name by which this connection is referred to
  when using the \fBconsole\fP program.
  This is typically the name of the host whose console is being monitored.
+ .PP
+ The next field has one of three alternate forms:
  .TP
  .I device
! the full pathname of the device for this line.
  .TP
  .BI ! termserver
  the hostname of the terminal server to connect to.
***************
*** 56,61 ****
--- 56,76 ----
  .BI | command
  the command to invoke on the console server.
  .PP
+ The interpretation of the third field depends on the form of the second
+ field:
+ .TP
+ .I baud
+ When the second field is a full pathname to a device, the second field
+ is the speed and parity for this device.  The speed may be given as an
+ integer in bits per second.  The desired parity setting for this device
+ is specified by the first letter of any of:  even, odd, mark, space, or
+ none, given immediately after the speed number.
+ .TP
+ .I port
+ When the second field is the hostname of a terminal server (i.e. begins
+ with a `!' character), the second field is the TCP port number to
+ connect to on that host.
+ .PP
  \fIdevice\fP, !\fItermserver\fP, and |\fIcommand\fP may be followed by
  a remote console server name in the form ``\fB@\fP\fIconserver\fP'',
  in which case the conserver daemon will send connections for \fIname\fP
***************
*** 91,104 ****
  specifies `lines' and will cause timestamps of the form
  `[Mon Jan 25 14:46:56 PST 1999]' to
  be placed every \fImark-interval\fP lines (a newline character signifies
! a new line). So, `5h' specifies every five hours and `2l' specifies every
! two lines.
! An `\fBa\fP' can be specified to add logs of
  `attached', `detached', and `bumped' actions,
  including the user's name and the host from which the
  \fBconsole\fP connection was made,
  to the logfile.
! A `\fBb\fP' can be specified to add logging of break sequences sent
  to the console.
  .IP
  A default \fItimestamp-spec\fP can be specified by using the
--- 106,118 ----
  specifies `lines' and will cause timestamps of the form
  `[Mon Jan 25 14:46:56 PST 1999]' to
  be placed every \fImark-interval\fP lines (a newline character signifies
! a new line).
! An `\fBa\fP' flag can be specified to add logs of
  `attached', `detached', and `bumped' actions,
  including the user's name and the host from which the
  \fBconsole\fP connection was made,
  to the logfile.
! A `\fBb\fP' flag can be specified to add logging of break sequences sent
  to the console.
  .IP
  A default \fItimestamp-spec\fP can be specified by using the
***************
*** 158,164 ****
  .PD
  .PP
  This section is terminated with a `\fB%%\fP' token on a line by itself.
! .PP
  The next section of the file contains a list of hosts and addresses
  which are allowed to connect to the console server.
  .B Conserver
--- 172,178 ----
  .PD
  .PP
  This section is terminated with a `\fB%%\fP' token on a line by itself.
! .SS "Access Specifications"
  The next section of the file contains a list of hosts and addresses
  which are allowed to connect to the console server.
  .B Conserver

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>

From woods@proven.weird.com Wed Apr 24 18:40:22 2002
Received: from most.weird.com (IDENT:0a8Zmb0fPlKu8FmOR4cw3uyFStnL/zXVSNspDpp2ousukoBRyKscmJJr9RKvKXmrO52JczSV8T4@mail.weird.com [204.92.254.2])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g3P1eL2S018819
	for <users@conserver.com>; Wed, 24 Apr 2002 18:40:21 -0700 (PDT)
Received: from proven.weird.com([204.92.254.15]) (1994 bytes) by most.weird.com
	via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp
	(sender: <woods@proven.weird.com>) 
	(ident <[P95I9sH/VejcFzaIBQV395grDcwpPBXCtYR5ZcCI4yPFJA5AHG8oor3088kFzFNyeCnFnZcF2zl7rqoRUQPv6g==]> using rfc1413)
	id <m170YFA-000g6PC@most.weird.com>
	for <users@conserver.com>; Wed, 24 Apr 2002 21:40:20 -0400 (EDT)
	(Smail-3.2.0.115-Pre 2001-Aug-6 #2 built 2002-Apr-22)
Received: by proven.weird.com (Postfix, from userid 1000)
	id 398AEAC; Wed, 24 Apr 2002 21:40:19 -0400 (EDT)
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: woods@weird.com (Greg A. Woods)
To: users@conserver.com (ConServer Users Mailing List)
Subject: proposal for remote console specs using the console name, not device name
X-Mailer: VM 7.03 under Emacs 21.2.1
Reply-To: users@conserver.com (ConServer Users Mailing List)
Organization: Planix, Inc.; Toronto, Ontario; Canada
Message-Id: <20020425014019.398AEAC@proven.weird.com>
Date: Wed, 24 Apr 2002 21:40:19 -0400 (EDT)
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

I'd like to propose that remote console specifications (the "@conserver"
form) should be preceded by the remote conserver's name for the console,
not it's device name.  [and until the next major release both could be
permitted, with a warning logged for deprecated usage....]

I was hoping I could attach a proposed patch to implement this, but I've
not yet learned enough about the internals of conserver to whip this up
so quickly, and meanwhile I think I've found the place where I need to
add my send/expect termserver login code (POKE_ANNEX) and I'd better get
working on that instead....  now to figure out how to specify this in
the config....

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>

From djs@certaintysolutions.com Wed Apr 24 23:46:28 2002
Received: from yosemite.rwc.gnac.net (yosemite.rwc.gnac.net [198.151.248.221])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g3P6kS2S021031
	for <users@conserver.com>; Wed, 24 Apr 2002 23:46:28 -0700 (PDT)
Received: by yosemite.rwc.gnac.net; id XAA20600; Wed, 24 Apr 2002 23:46:27 -0700 (PDT)
Received: from unknown(192.168.1.21) by yosemite.rwc.gnac.net via smap (V5.0)
	id xma019136; Wed, 24 Apr 02 23:46:08 -0700
Received: from tweety.main.gnac.com (localhost.main.gnac.com [127.0.0.1]) 
  by pepe.corp.gnac.com (8.11.0/8.8.7/GNAC-GW-2.1) with ESMTP id g3P6jQx00121
  for <users@conserver.com>; Wed, 24 Apr 2002 23:45:26 -0700 (PDT)
Received: 
  by tweety.main.gnac.com (8.9.3/8.7.3/GNAC-COM-1.1) id XAA09745 
  for users@conserver.com; Wed, 24 Apr 2002 23:46:06 -0700 (PDT)
Message-Id: <200204250646.XAA09745@tweety.main.gnac.com>
From: djs@gnac.com (Dave Stuit)
Date: Wed, 24 Apr 2002 23:46:06 -0700
In-Reply-To: <20020425014019.398AEAC@proven.weird.com>;
       from Greg A. Woods on 24 Apr 02 18:41 PDT
Organization: GNAC, currently Certainty Solutions
X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98)
To: users@conserver.com
Subject: Re: proposal for remote console specs using the console name, not device name
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

On 24 Apr 02 18:41 PDT, Greg A. Woods wrote:
>
>I'd like to propose that remote console specifications (the "@conserver"
>form) should be preceded by the remote conserver's name for the console,
>not it's device name.  [and until the next major release both could be
>permitted, with a warning logged for deprecated usage....]

I can see how that would make things easier for multiple conserver hosts
with separately maintained cf files (although i'm not sure when it would
be desirable for different conservers to refer to a console by different
names ... seems like that would be confusing).

However, i know of at least a few sites where a single cf file is
maintained centrally and distributed to all conserver hosts (and we like
it that way :) ).  Also, if one of the hosts dies, it's especially easy
to have another one take over if all of the device and port information
is present in everyone's cf file (assuming the devices are terminal
servers that are accessible from the other conserver hosts).

Since conserver running on any given host only cares about the device
info in the cf file entries that it's controlling, i wouldn't think
it would be hard to modify the parser to permit the device name to be
omitted from the remote entries (assuming it's considered an error now).
And i suppose it could be taken a step further to allow a different remote
console name to be specified (perhaps if the "device" starts with none of
[/!|]).  But that could require some code (and protocol) changes where
the client is referred to a remote conserver.  Also remember that the
console client will talk to multiple servers to get the information it
needs for options like "-w", so it'll be really hard to hide the remote
console names.

It's all fine with me, just as long as it doesn't break the existing
functionality, with remote names defaulting to the local names. :)

--dave

From MHEE@fuji-ef.nl Fri Apr 26 01:57:22 2002
Received: from efwall.fuji-ef.nl ([193.202.98.70])
	by underdog.stansell.org (8.12.2/8.12.2) with SMTP id g3Q8vK2S010280
	for <users@conserver.com>; Fri, 26 Apr 2002 01:57:21 -0700 (PDT)
Received: by efwall.fuji-ef.nl; (5.65v4.0/1.3/18Jul98) id AA19278; Fri, 26 Apr 2002 10:57:34 +0200
Received: from somewhere by smtpxd
Message-Id: <8212F48C24DAD511B55F0002A5AAF4B102A33359@ftilmail.fuji-ef.nl>
From: Marcel Heemst van <MHEE@fuji-ef.nl>
To: "'users@conserver.com'" <users@conserver.com>
Subject: Problems with up and down going connections
Date: Fri, 26 Apr 2002 10:57:19 +0200
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

Hello,

I have a problem with consoleserver 7.2.0 or lower versions.
When our terminal server is down and we start the conserver; console -u
detect the connections down
When out terminal server is up and we start the conserver; console -u detect
the connections up.
But...
When the terminal server is going down and the conserver was already
started, console -u NEVER detect the connections down.
AND
When the terminal server is going up and the conserver was  already started,
console -u NEVER detect the connection up.

This problem can we solve with:
Start a console session to this port and use the ^Eco string.

But we want to have a functionality to redetect the connection state
automaticly, because we have an another application which is detect the
connection state and generate alarm then the connection is down.

I hope somebody can help me.....

Regards,
Marcel van Heemst 

From bryan@conserver.com Sun Apr 28 00:05:07 2002
Received: from underdog.stansell.org (localhost [127.0.0.1])
	by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g3S7572S003907
	for <users@conserver.com>; Sun, 28 Apr 2002 00:05:07 -0700 (PDT)
Received: (from nobody@localhost)
	by underdog.stansell.org (8.12.2/8.12.2/Submit) id g3S757BD003906
	for users@conserver.com; Sun, 28 Apr 2002 00:05:07 -0700 (PDT)
X-Authentication-Warning: underdog.stansell.org: nobody set sender to bryan@conserver.com using -f
To: users@conserver.com
Subject: Re: Problems with up and down going connections
Message-ID: <1019977507.3ccb9f2359da0@www.stansell.org>
Date: Sun, 28 Apr 2002 00:05:07 -0700 (PDT)
From: bryan@conserver.com
References: <8212F48C24DAD511B55F0002A5AAF4B102A33359@ftilmail.fuji-ef.nl>
In-Reply-To: <8212F48C24DAD511B55F0002A5AAF4B102A33359@ftilmail.fuji-ef.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.7
X-Originating-IP: 210.54.226.226
Sender: users-admin@conserver.com
Errors-To: users-admin@conserver.com
X-BeenThere: users@conserver.com
X-Mailman-Version: 2.0.8
Precedence: bulk
List-Help: <mailto:users-request@conserver.com?subject=help>
List-Post: <mailto:users@conserver.com>
List-Subscribe: <https://www.conserver.com/mailman/listinfo/users>,
	<mailto:users-request@conserver.com?subject=subscribe>
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/>

Quoting Marcel Heemst van <MHEE@fuji-ef.nl>:
> But...
> When the terminal server is going down and the conserver was already
> started, console -u NEVER detect the connections down.
> AND
> When the terminal server is going up and the conserver was  already
> started,
> console -u NEVER detect the connection up.

This is true.  The first issue is that the conserver host isn't seeing any 
problem with the TCP connection to the terminal server.  If the TCP session 
goes down, conserver will notice the problem and bring the consoles to the down 
state (and try and reconnect, actually).  Usually it only happens when a 
terminal server crashes or gets power cycled (it doesn't have a chance to abort 
all the TCP connections).  There's really not much that can be done here, since 
conserver is relying on the underlying TCP stack to do it's job - most 
applications would have this same problem (if you were to connect to one of 
those consoles and try and interact with it, conserver would immediately get a 
TCP failure and bring it down - after trying to reconnect).  The idea of having 
conserver "ping" the terminal servers to make sure they're up doesn't really 
appeal to me (right at this moment), but maybe someone would have a good idea 
of how to do this - that way terminal servers that drop off the net (for 
whatever reason) would be detected sooner.  But, ideally, this is a small edge 
case and not the norm (rebooting a terminal server *should* trigger TCP session 
closures - at least, if the terminal server was doing "the right thing").

As for the second problem (conserver already running and a terminal server is 
booted), there are a couple of options.  The first is to use another app to 
watch your terminal servers and send conserver a SIGUSR1 whenever it wants 
conserver to try and reconnect to all the consoles marked as down.  Another 
option is to use the -o/-O options and have conserver automatically try and 
reconnect all the downed consoles.  Between those two methods, I hope something 
works for you.

> This problem can we solve with:
> Start a console session to this port and use the ^Eco string.
> 
> But we want to have a functionality to redetect the connection state
> automaticly, because we have an another application which is detect
> the
> connection state and generate alarm then the connection is down.

Hopefully one of those methods above works in this case.

Bryan