From aaron@osdl.org Mon Jan 6 16:22:44 2003 Received: from mail.osdl.org (air-2.osdl.org [65.172.181.6]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h070MheV003374 for ; Mon, 6 Jan 2003 16:22:43 -0800 (PST) Received: from osdlab.pdx.osdl.net (osdlab.pdx.osdl.net [172.20.1.28]) by mail.osdl.org (8.11.6/8.11.6) with ESMTP id h070Mbv19830 for ; Mon, 6 Jan 2003 16:22:38 -0800 Date: Mon, 6 Jan 2003 16:22:37 -0800 (PST) From: Aaron Burt X-X-Sender: To: Subject: Reconnect causes slowdown in 7.2.1 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Well, I'd been trying for quite a while to find the cause of random slowdowns on some (but not all) of my console connections. The slowness is in the response time of console connections. This includes things like the time it takes to make the initial connection (time from typing "console dev4-001" to getting a "[Enter `^Ec?' for help]") or, once you're connected, from hitting a key and getting a response from the machine you're connected to. The slowness affects all 16 consoles managed by a given Conserver process. What I found was that if a terminal server was rejecting reverse-telnet connections on even one port managed by a Conserver process, it'd slow 'em all down. Now the reinit wasn't happening immediately. It'd be attempted every few seconds, so the load should be negligible. And it didn't seem to bog the rest of the host down, just that one Conserver process. So, is this problem addressed by the reinit changes in 7.2.3? Or does the sleep in the reinit loop hold up the whole Conserver process? Thanks in advance, Aaron Burt Open Source Development Lab From bryan@stansell.org Mon Jan 6 23:17:32 2003 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h077HWeV006859 for ; Mon, 6 Jan 2003 23:17:32 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.7/8.12.7/Submit) id h077HVlq006858 for users@conserver.com; Mon, 6 Jan 2003 23:17:31 -0800 (PST) Date: Mon, 6 Jan 2003 23:17:31 -0800 From: Bryan Stansell To: users@conserver.com Subject: Re: Reconnect causes slowdown in 7.2.1 Message-ID: <20030107071731.GA6415@underdog.stansell.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: On Mon, Jan 06, 2003 at 04:22:37PM -0800, Aaron Burt wrote: > The slowness is in the response time of console connections. This > includes things like the time it takes to make the initial connection > (time from typing "console dev4-001" to getting a "[Enter `^Ec?' for > help]") or, once you're connected, from hitting a key and getting a > response from the machine you're connected to. are we talking about a second or more like 10 second delays? see below for more. > The slowness affects all 16 consoles managed by a given Conserver process. that makes sense...when a process is "busy" waiting, it'll hang the group of consoles it's managing. > So, is this problem addressed by the reinit changes in 7.2.3? i'd have to say no. i believe most things are the same in regards to this issue, but, of course, there are other things the new stuff has that could be useful. but, i'm digressing. > Or does the sleep in the reinit loop hold up the whole Conserver process? there are a couple of sleep() calls that would hold up a conserver process. each are less than a second, however, and i'd really be surprised if they were "stacking up" and giving you long pauses (although a second can seem like a long time too). if you're seeing very long pauses, it's more likely the call to connect() that's hanging. was your terminal server actively rejecting the reverse-telnet connections, or is it just half-opening the socket? if it's not getting an active rejection, you'll see a 10 second delay before the conserver process gives up and decides to move on - any other consoles managed by that process will hang since it's not multi-threaded or anything (this would be an ideal place to optimize conserver's functionality with threads). if you think it's a connect() issue, you can use the --with-timeout flag to reduce the delay to a smaller value (like 1) as a work-around - just make sure your normal terminal server response time is below that value. if none of this seems to help, you could try tracing the process and seeing where, exactly, these long delays occur. or even running in debug mode could help track it down. if we can narrow down what part of the code is actually the culprit, perhaps it can be changed to be less devastating. Bryan From aaron@osdl.org Tue Jan 7 15:49:39 2003 Received: from mail.osdl.org (air-2.osdl.org [65.172.181.6]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h07NnceV018244 for ; Tue, 7 Jan 2003 15:49:39 -0800 (PST) Received: from osdlab.pdx.osdl.net (osdlab.pdx.osdl.net [172.20.1.28]) by mail.osdl.org (8.11.6/8.11.6) with ESMTP id h07NnXv13527 for ; Tue, 7 Jan 2003 15:49:33 -0800 Date: Tue, 7 Jan 2003 15:49:33 -0800 (PST) From: Aaron Burt X-X-Sender: To: Subject: Re: Reconnect causes slowdown in 7.2.1 In-Reply-To: <20030107071731.GA6415@underdog.stansell.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: On Mon, 6 Jan 2003, Bryan Stansell wrote: > On Mon, Jan 06, 2003 at 04:22:37PM -0800, Aaron Burt wrote: > > The slowness is in the response time of console connections. This > > includes things like the time it takes to make the initial connection > > (time from typing "console dev4-001" to getting a "[Enter `^Ec?' for > > help]") or, once you're connected, from hitting a key and getting a > > response from the machine you're connected to. > > are we talking about a second or more like 10 second delays? see below > for more. >From 1+ up to about 18 seconds to connect, depending on how many consoles are in reinit. Keystroke-to-host response times are typically about half the connect time. I timed by counting seconds, so the accuracy leaves something to be desired. Strangely, Conserver commands and responses took around 2 seconds consistently wheter 1 or 7 consoles were in reinit. This was true for ^Ec commands and for "console down" messages when sending keystrokes to downed consoles. > > The slowness affects all 16 consoles managed by a given Conserver process. > > that makes sense...when a process is "busy" waiting, it'll hang the > group of consoles it's managing. That's a shame. > > So, is this problem addressed by the reinit changes in 7.2.3? > > i'd have to say no. i believe most things are the same in regards to > this issue, but, of course, there are other things the new stuff has > that could be useful. but, i'm digressing. Indeed. The ability to turn off auto-reinit, for one. I'll have to see if I can find a way to dump a list of consoles in reinit and to force a console down/up. With that, I should be able to automagically find and fix blocked ports, which is a common problem after network outages and suchlike. > > Or does the sleep in the reinit loop hold up the whole Conserver process? > > there are a couple of sleep() calls that would hold up a conserver > process. each are less than a second, however, and i'd really be > surprised if they were "stacking up" and giving you long pauses That's what they appear to be doing. I found a group that had around 7 ports in reinit, and the delay decreased in a linear fashion as I brought ports out of reinit. The reinit retries also happened faster as fewer ports were in reinit. > (although a second can seem like a long time too). if you're seeing > very long pauses, it's more likely the call to connect() that's > hanging. was your terminal server actively rejecting the > reverse-telnet connections, or is it just half-opening the socket? It was sending "port in use" or some such and then dropping the connection. From cfowler@outpostsentinel.com Wed Jan 8 12:09:09 2003 Received: from cfowler.outpostsentinel.com (dsl-64-129-133-253.telocity.com [64.129.133.253]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h08K98eV001223 for ; Wed, 8 Jan 2003 12:09:09 -0800 (PST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id h08KBnk09642 for ; Wed, 8 Jan 2003 15:11:49 -0500 Subject: MAXMEMB From: cfowler To: users@conserver.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 08 Jan 2003 15:11:48 -0500 Message-Id: <1042056709.1172.7.camel@cfowler.outpostsentinel.com> Mime-Version: 1.0 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Is there a technical reason that MAXMEMB's is limited to 16? I've changed mine to 96. From kenneth.g.stephens@intel.com Fri Jan 10 10:14:34 2003 Received: from caduceus.fm.intel.com (fmr02.intel.com [192.55.52.25]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0AIEXol015675 for ; Fri, 10 Jan 2003 10:14:34 -0800 (PST) Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37]) by caduceus.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h0AI25j16131 for ; Fri, 10 Jan 2003 18:02:05 GMT Received: from fmsmsxvs041.fm.intel.com (fmsmsxvs041.fm.intel.com [132.233.42.126]) by petasus.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.27 2002/10/16 23:46:59 dmccart Exp $) with SMTP id h0AHmKE13506 for ; Fri, 10 Jan 2003 17:48:20 GMT Received: from fmsmsx28.fm.intel.com ([132.233.42.28]) by fmsmsxvs041.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003011009511512796 for ; Fri, 10 Jan 2003 09:51:15 -0800 Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 10 Jan 2003 09:53:10 -0800 Message-ID: From: "Stephens, Kenneth G" To: users@conserver.com Subject: Read Only Roller Coaster Date: Fri, 10 Jan 2003 09:52:56 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message 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.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Everytime I search for read-only, I get what a feature it is. However, when I invoke console, that's all I get. #console system console: console: [read-only -- use ^E c ? for help] [read-only -- use ^E c ? for help] # No chance to do anything, just a roller coaster through the application. conserver.cf system:/dev/ttyD000:9600n:&:1h %% trusted: 127.0.0.1 hostname allowed: 127.0.0.1 hostname #fini conserver.passwd any:*passwd*:any #fini Any ideas? Ken From kenneth.g.stephens@intel.com Fri Jan 10 11:59:40 2003 Received: from hermes.fm.intel.com (fmr01.intel.com [192.55.52.18]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0AJxeol016512 for ; Fri, 10 Jan 2003 11:59:40 -0800 (PST) Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37]) by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h0AJv7L08974 for ; Fri, 10 Jan 2003 19:57:07 GMT Received: from fmsmsxvs041.fm.intel.com (fmsmsxvs041.fm.intel.com [132.233.42.126]) by petasus.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.27 2002/10/16 23:46:59 dmccart Exp $) with SMTP id h0AItuV13051 for ; Fri, 10 Jan 2003 18:55:56 GMT Received: from fmsmsx28.fm.intel.com ([132.233.42.28]) by fmsmsxvs041.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003011010585005015 ; Fri, 10 Jan 2003 10:58:50 -0800 Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 10 Jan 2003 11:00:45 -0800 Message-ID: From: "Stephens, Kenneth G" To: jrj@purdue.edu Cc: users@conserver.com Subject: RE: Read Only Roller Coaster Date: Fri, 10 Jan 2003 11:00:30 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message 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.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: -----Original Message----- From: John R. Jackson [mailto:jrj@purdue.edu] Sent: Friday, January 10, 2003 10:59 AM To: Stephens, Kenneth G Cc: users@conserver.com Subject: Re: Read Only Roller Coaster >Everytime I search for read-only, I get what a feature it is. However, when >I invoke console, that's all I get. > >#console system >console: console: [read-only -- use ^E c ? for help] >[read-only -- use ^E c ? for help] ># > >No chance to do anything, just a roller coaster through the application. Not entirly sure I understand your question, but new connections will be put in read-only mode if the server already has a connection in read-write mode. What happens if you do ^Ecw to see who else is connected? What about ^Ecf to force you into read-write? >Ken John R. Jackson, Technical Software Specialist, jrj@purdue.edu From kenneth.g.stephens@intel.com Fri Jan 10 11:59:56 2003 Received: from hermes.fm.intel.com (fmr01.intel.com [192.55.52.18]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0AJxuol016516 for ; Fri, 10 Jan 2003 11:59:56 -0800 (PST) Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37]) by hermes.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h0AJvNL09110 for ; Fri, 10 Jan 2003 19:57:24 GMT Received: from fmsmsxvs041.fm.intel.com (fmsmsxvs041.fm.intel.com [132.233.42.126]) by petasus.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.27 2002/10/16 23:46:59 dmccart Exp $) with SMTP id h0AIuwV13502 for ; Fri, 10 Jan 2003 18:56:58 GMT Received: from fmsmsx28.fm.intel.com ([132.233.42.28]) by fmsmsxvs041.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003011010595309930 ; Fri, 10 Jan 2003 10:59:53 -0800 Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 10 Jan 2003 11:01:48 -0800 Message-ID: From: "Stephens, Kenneth G" To: jrj@purdue.edu Cc: users@conserver.com Subject: RE: Read Only Roller Coaster Date: Fri, 10 Jan 2003 11:01:44 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message 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.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Does not give me chance to do anything. System has been rebooted and services restarted. Doing this as root. Thanks for the reply. Ken -----Original Message----- From: John R. Jackson [mailto:jrj@purdue.edu] Sent: Friday, January 10, 2003 10:59 AM To: Stephens, Kenneth G Cc: users@conserver.com Subject: Re: Read Only Roller Coaster >Everytime I search for read-only, I get what a feature it is. However, when >I invoke console, that's all I get. > >#console system >console: console: [read-only -- use ^E c ? for help] >[read-only -- use ^E c ? for help] ># > >No chance to do anything, just a roller coaster through the application. Not entirly sure I understand your question, but new connections will be put in read-only mode if the server already has a connection in read-write mode. What happens if you do ^Ecw to see who else is connected? What about ^Ecf to force you into read-write? >Ken John R. Jackson, Technical Software Specialist, jrj@purdue.edu From jrj@gandalf.cc.purdue.edu Fri Jan 10 10:59:26 2003 Received: from gandalf.cc.purdue.edu (IDENT:root@gandalf.cc.purdue.edu [128.210.189.51]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0AIxQol016046 for ; Fri, 10 Jan 2003 10:59:26 -0800 (PST) Received: from gandalf.cc.purdue.edu (IDENT:jrj@localhost [127.0.0.1]) by gandalf.cc.purdue.edu (8.12.5/8.12.5) with ESMTP id h0AIxLKO023687; Fri, 10 Jan 2003 13:59:21 -0500 (EST) Message-Id: <200301101859.h0AIxLKO023687@gandalf.cc.purdue.edu> To: "Stephens, Kenneth G" cc: users@conserver.com Subject: Re: Read Only Roller Coaster In-reply-to: Your message of "Fri, 10 Jan 2003 09:52:56 PST." Reply-to: jrj@purdue.edu Date: Fri, 10 Jan 2003 13:59:21 -0500 From: "John R. Jackson" Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: >Everytime I search for read-only, I get what a feature it is. However, when >I invoke console, that's all I get. > >#console system >console: console: [read-only -- use ^E c ? for help] >[read-only -- use ^E c ? for help] ># > >No chance to do anything, just a roller coaster through the application. Not entirly sure I understand your question, but new connections will be put in read-only mode if the server already has a connection in read-write mode. What happens if you do ^Ecw to see who else is connected? What about ^Ecf to force you into read-write? >Ken John R. Jackson, Technical Software Specialist, jrj@purdue.edu From bryan@stansell.org Sun Jan 12 11:46:43 2003 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0CJkhol025206 for ; Sun, 12 Jan 2003 11:46:43 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.7/8.12.7/Submit) id h0CJkhXw025205 for users@conserver.com; Sun, 12 Jan 2003 11:46:43 -0800 (PST) Date: Sun, 12 Jan 2003 11:46:43 -0800 From: Bryan Stansell To: users@conserver.com Subject: Re: Read Only Roller Coaster Message-ID: <20030112194643.GB24836@underdog.stansell.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: there's one other possibility. if the local device has permissions that are read-only for the user running conserver, you'll get read-only connections to the console (since it can't open the port read-write). so, what are the perms on /dev/ttyD000? 444? if you temporarily change them to 777 and start conserver, does it fix the problem? just a wild guess. aside from this and the already mentioned "another user", i can't think of a reason why you'd get read-only connections (well, aside from a bizarre bug). hope this helps. Bryan On Fri, Jan 10, 2003 at 09:52:56AM -0800, Stephens, Kenneth G wrote: > system:/dev/ttyD000:9600n:&:1h From bryan@stansell.org Sun Jan 12 12:08:58 2003 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0CK8wol025556 for ; Sun, 12 Jan 2003 12:08:58 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.7/8.12.7/Submit) id h0CK8wj5025555 for users@conserver.com; Sun, 12 Jan 2003 12:08:58 -0800 (PST) Date: Sun, 12 Jan 2003 12:08:58 -0800 From: Bryan Stansell To: users@conserver.com Subject: Re: MAXMEMB Message-ID: <20030112200858.GD24836@underdog.stansell.org> References: <1042056709.1172.7.camel@cfowler.outpostsentinel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1042056709.1172.7.camel@cfowler.outpostsentinel.com> User-Agent: Mutt/1.4i Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: On Wed, Jan 08, 2003 at 03:11:48PM -0500, cfowler wrote: > Is there a technical reason that MAXMEMB's is limited to 16? I've > changed mine to 96. the big reason (and a main reason for multiple processes) is the maximum number of open files a process can have. each console can have a few file descriptors associated with it (device, logfile, connected users, and socket). so, off the top of my head that would be ( 2 * consoles + users + 1 ). you also have the speed of your conserver host vs the rates at which data could be streaming to it. go back a decade and this was probably more of an issue than today, but it's still something to think about. and then you have the problem recently mentioned about delays. if any of the 96 console connections "lock up", it'll delay all activity on the 96 consoles. with 16, there's less of an impact (but, obviously there is an impact, based on the outstanding question of the delays). this can be an issue once the server comes up or during startup - with 16 per process you get a bit of parallelization during startup. so, is there any reason not to up the number to 96? no. assuming you know the risks and weigh things appropriately. if i remember right, i've upped the number to 48 at some sites. but that was mainly to reduce the memory footprint in older versions of the code which had staticly allocated buffers. no need to worry about that with the current code. personally, i wouldn't change from 16 unless there was a really good reason (like wanting to only have one child process for firewall rules or some such reason). Bryan From bryan@stansell.org Sun Jan 12 12:21:28 2003 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0CKLSol025756 for ; Sun, 12 Jan 2003 12:21:28 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.7/8.12.7/Submit) id h0CKLSsw025755 for users@conserver.com; Sun, 12 Jan 2003 12:21:28 -0800 (PST) Date: Sun, 12 Jan 2003 12:21:28 -0800 From: Bryan Stansell To: users@conserver.com Subject: Re: Reconnect causes slowdown in 7.2.1 Message-ID: <20030112202128.GE24836@underdog.stansell.org> References: <20030107071731.GA6415@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: On Tue, Jan 07, 2003 at 03:49:33PM -0800, Aaron Burt wrote: > >From 1+ up to about 18 seconds to connect, depending on how many consoles > are in reinit. Keystroke-to-host response times are typically about half > the connect time. I timed by counting seconds, so the accuracy leaves > something to be desired. > > Strangely, Conserver commands and responses took around 2 seconds > consistently wheter 1 or 7 consoles were in reinit. This was true for > ^Ec commands and for "console down" messages when sending keystrokes to > downed consoles. ok...this is very bizarre (well, unexpected in my mind), but there has to be a good reason for it. what, i don't know, but maybe we can track it down. > Indeed. The ability to turn off auto-reinit, for one. I'll have to see > if I can find a way to dump a list of consoles in reinit and to force a > console down/up. With that, I should be able to automagically find and > fix blocked ports, which is a common problem after network outages and > suchlike. the 'console -i' output shows lots of data and is there for just this purpose. hopefully it has enough for what you need. > > (although a second can seem like a long time too). if you're seeing > > very long pauses, it's more likely the call to connect() that's > > hanging. was your terminal server actively rejecting the > > reverse-telnet connections, or is it just half-opening the socket? > > It was sending "port in use" or some such and then dropping the > connection. that helps. then, yeah, you're hitting just about every sleep call and probably in rapid succession. it still would be interesting to see truss/strace/whatever output of a child process that was busily trying to bring up a port. and you would benefit from the new code in that you could turn off the immediate auto-bringup of the console and let it kick in only every minute or longer. so, i *think*, now that i'm at the end of your message, that i understand what's going on. at least, i have a good guess (your note of it getting a 'port in use' and being dropped was the key). if you're logging all those ports, you should have a heck of a set of large logfiles, huh? aside from the "work-around" possibilities (like the new-for-you auto-retry options), i don't have much else that can help. but it is making me think of ways to redo the code so i can get rid of the sleep statements and, hopefully, reduce or remove the noticable delays. dunno if or when it'll become code, so try the work-arounds for now. Bryan From cfowler@outpostsentinel.com Mon Jan 13 05:47:18 2003 Received: from cfowler.outpostsentinel.com (dsl-64-129-133-253.telocity.com [64.129.133.253]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0DDlHol007417; Mon, 13 Jan 2003 05:47:17 -0800 (PST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id h0DDoHk06894; Mon, 13 Jan 2003 08:50:18 -0500 Subject: Re: MAXMEMB From: cfowler To: Bryan Stansell Cc: users@conserver.com In-Reply-To: <20030112200858.GD24836@underdog.stansell.org> References: <1042056709.1172.7.camel@cfowler.outpostsentinel.com> <20030112200858.GD24836@underdog.stansell.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 13 Jan 2003 08:50:17 -0500 Message-Id: <1042465818.6691.4.camel@cfowler.outpostsentinel.com> Mime-Version: 1.0 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: I'll give more insight to why I did this. It is almost impossible for me to gain access to my consoles over a firewall. You see the the main process offers me port 1024 then adds 1 each new connection. I can not open up 1024 - 1096 or whatever on my firewall. What we've done is made it simple. Now the process only uses 783 and 782 ports and no more. This may not be an issue for some but was for us. Maybe this behavior is something that can be looked at in 8.0 version. Having 2 possible ports are okay but having a N number of possible ports, IMHO are not. On Sun, 2003-01-12 at 15:08, Bryan Stansell wrote: > On Wed, Jan 08, 2003 at 03:11:48PM -0500, cfowler wrote: > > Is there a technical reason that MAXMEMB's is limited to 16? I've > > changed mine to 96. > > the big reason (and a main reason for multiple processes) is the > maximum number of open files a process can have. each console can have > a few file descriptors associated with it (device, logfile, connected > users, and socket). so, off the top of my head that would be ( 2 * > consoles + users + 1 ). > > you also have the speed of your conserver host vs the rates at which > data could be streaming to it. go back a decade and this was probably > more of an issue than today, but it's still something to think about. > > and then you have the problem recently mentioned about delays. if any > of the 96 console connections "lock up", it'll delay all activity on > the 96 consoles. with 16, there's less of an impact (but, obviously > there is an impact, based on the outstanding question of the delays). > this can be an issue once the server comes up or during startup - with > 16 per process you get a bit of parallelization during startup. > > so, is there any reason not to up the number to 96? no. assuming you > know the risks and weigh things appropriately. if i remember right, > i've upped the number to 48 at some sites. but that was mainly to > reduce the memory footprint in older versions of the code which had > staticly allocated buffers. no need to worry about that with the > current code. personally, i wouldn't change from 16 unless there was a > really good reason (like wanting to only have one child process for > firewall rules or some such reason). > > Bryan > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users From iainr@inf.ed.ac.uk Mon Jan 13 06:00:05 2003 Received: from topper.inf.ed.ac.uk (topper.inf.ed.ac.uk [129.215.32.40]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0DE04ol007553 for ; Mon, 13 Jan 2003 06:00:05 -0800 (PST) Received: from inf.ed.ac.uk (IDENT:iainr@testnode2.inf.ed.ac.uk [129.215.32.124]) by topper.inf.ed.ac.uk (8.11.6/8.11.6) with ESMTP id h0DE02427608 for ; Mon, 13 Jan 2003 14:00:02 GMT Message-ID: <3E22C662.3020102@inf.ed.ac.uk> Date: Mon, 13 Jan 2003 14:00:02 +0000 From: Iain Rae User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.2) Gecko/20021128 X-Accept-Language: en-us, en MIME-Version: 1.0 To: users@conserver.com Subject: Re: MAXMEMB References: <1042056709.1172.7.camel@cfowler.outpostsentinel.com> <20030112200858.GD24836@underdog.stansell.org> <1042465818.6691.4.camel@cfowler.outpostsentinel.com> In-Reply-To: <1042465818.6691.4.camel@cfowler.outpostsentinel.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: cfowler wrote: > I'll give more insight to why I did this. It is almost impossible for > me to gain access to my consoles over a firewall. You see the the main > process offers me port 1024 then adds 1 each new connection. I can not > open up 1024 - 1096 or whatever on my firewall. What we've done is made > it simple. Now the process only uses 783 and 782 ports and no more. > This may not be an issue for some but was for us. Maybe this behavior > is something that can be looked at in 8.0 version. Having 2 possible > ports are okay but having a N number of possible ports, IMHO are not. > If you only have one console server you could ssh onto the console server and run console via the loopback address. Doing it with more that one is also possible (but a bit convoluted). -- Iain Rae Tel:01316505202 Computing Officer JCMB:2418 School of Informatics The University of Edinburgh From woods@proven.weird.com Mon Jan 13 10:55:13 2003 Received: from most.weird.com (IDENT:KSdsdhdngb2juJjV/gCBFYlFfQHrDEdAqxgs26VnbhMk84+/Ti7zRaiN6m3dxYSWi2tCluaxtHw@most.weird.com [204.92.254.2]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0DItDol009825 for ; Mon, 13 Jan 2003 10:55:13 -0800 (PST) Received: from proven.weird.com([204.92.254.15]) (2790 bytes) by most.weird.com via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident <[J60DsuB3d7cZBhX7EwIcpNB7Qdh6j8jmEcvKUK35pQjDjlMyXr/fqAzRtY0Bq8ElhPpBQQsNgboxYgNX1l9Wyg==]> using rfc1413) id for ; Mon, 13 Jan 2003 13:55:11 -0500 (EST) (Smail-3.2.0.115-Pre 2001-Aug-6 #7 built 2003-Jan-12) Received: by proven.weird.com (Postfix, from userid 1000) id A0271A; Mon, 13 Jan 2003 13:55:09 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: ;j3Eth2XV8h1Yfu*uL{<:dQ$#E[DB0gemGZJ"J#4fH*][ lz;@-iwMv_u\6uIEKR0KY"=MzoQH#CrqBN`nG_5B@rrM8,f~Gr&h5a\= To: cfowler Cc: users@conserver.com Subject: Re: conserver through a firewall? In-Reply-To: <1042465818.6691.4.camel@cfowler.outpostsentinel.com> References: <1042056709.1172.7.camel@cfowler.outpostsentinel.com> <20030112200858.GD24836@underdog.stansell.org> <1042465818.6691.4.camel@cfowler.outpostsentinel.com> X-Mailer: VM 7.07 under Emacs 21.2.1 Reply-To: users@conserver.com (ConServer Users Mailing List) Organization: Planix, Inc.; Toronto, Ontario; Canada Message-Id: <20030113185509.A0271A@proven.weird.com> Date: Mon, 13 Jan 2003 13:55:09 -0500 (EST) Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: [ On , January 13, 2003 at 08:50:17 (-0500), cfowler wrote: ] > Subject: Re: MAXMEMB > > I'll give more insight to why I did this. It is almost impossible for > me to gain access to my consoles over a firewall. You see the the main > process offers me port 1024 then adds 1 each new connection. I can not > open up 1024 - 1096 or whatever on my firewall. What we've done is made > it simple. Now the process only uses 783 and 782 ports and no more. > This may not be an issue for some but was for us. Maybe this behavior > is something that can be looked at in 8.0 version. Having 2 possible > ports are okay but having a N number of possible ports, IMHO are not. I would suggest that even if you have really secure SSL configuration integrated into your conserver clients you still really shouldn't be trying to access conserver through a firewall (normally SSL only provides privacy, not authentication (and certainly not easy-to-use authentication), and conserver's own authentication mechanisms are not really strong enough to use from a really remote client. You should probably have some secure host on the inside that you can login with SSH to and then use the console client from there. -- Greg A. Woods +1 416 218-0098; ; Planix, Inc. ; VE3TCP; Secrets of the Weird From ernie.oporto@viragelogic.com Tue Jan 14 11:18:24 2003 Received: from webshield.viragelogic.com (65-161-163-98-sprint-fm.viragelogic.com [65.161.163.98]) by underdog.stansell.org (8.12.7/8.12.7) with SMTP id h0EJIOol024762 for ; Tue, 14 Jan 2003 11:18:24 -0800 (PST) Received: from nj-eoporto-dt.nj.viragelogic.com(10.202.0.20) by webshield.viragelogic.com via csmap id 12899; Tue, 14 Jan 2003 11:20:34 -0800 (PST) Message-ID: <3E246279.72EC9971@viragelogic.com> Date: Tue, 14 Jan 2003 14:18:17 -0500 From: Ernie Oporto Organization: Virage Logic Corporation X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: users@conserver.com Subject: How to tell Sun keyboard console from serial console? Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms117E192E22D0009838080896" Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: This is a cryptographically signed message in MIME format. --------------ms117E192E22D0009838080896 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I there a way to tell whether a console is at the keyboard or at the serial port on a Sun machine? The "tty" command gives /dev/console for both. -- Ernest A. Oporto, Senior Systems Administrator Virage Logic Corporation http://www.viragelogic.com Perryville Corporate Park, Bldg 3, Clinton, NJ 08809 Phone:(908)735-1932 Fax:(908)735-1999 mailto:Ernie.Oporto@viragelogic.com --------------ms117E192E22D0009838080896 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIGAYJKoZIhvcNAQcCoIIICTCCCAUCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BeswggKrMIICFKADAgECAgMIUvEwDQYJKoZIhvcNAQEEBQAwgZIxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMjA5MjExNDUwMjdaFw0wMzA5MjExNDUwMjda MGcxDzANBgNVBAQTBk9wb3J0bzEPMA0GA1UEKhMGRXJuZXN0MRYwFAYDVQQDEw1Fcm5lc3Qg T3BvcnRvMSswKQYJKoZIhvcNAQkBFhxlcm5pZS5vcG9ydG9AdmlyYWdlbG9naWMuY29tMIGf MA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDFtoh2yKGfmF+AjjJYtcm7rhFaUyPgjf+npHIq BKiSPTMLbVnphnNUchCeEfUYUnCV6CLStwdq9/3N9T+HaxMsc99EwQWuWYJeVTv81kwHGC3s 7MJbiePioS8lijh9bgPjThI9hKAK8/0DUd3RVSAscGx6i2dnbA6BM3giSf3DEwIDAQABozkw NzAnBgNVHREEIDAegRxlcm5pZS5vcG9ydG9AdmlyYWdlbG9naWMuY29tMAwGA1UdEwEB/wQC MAAwDQYJKoZIhvcNAQEEBQADgYEArtIFKdI7LkOFxk4oU2vULQA1GWb0/5I8jE/q2zRnRVT9 i9vehSipFlibE2OdivlCZSY4KxdiTyKWZY+SzlQOaPKKPV+iPjn9OXCCmS9i+XCc9MVAuNWA UoblZek/gX6yGLP0VY3Daxxd6BzOFen/jLPEQjotZv49XJGjWuBYLTEwggM4MIICoaADAgEC AhBmRXK3zHT1z2N2RYTQLpEBMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMG A1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0 ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9u MSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEW HHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDAwODMwMDAwMDAwWhcNMDQwODI3 MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UE BxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNl cnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMwMIGfMA0G CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eBxdqIGYKXDuNEKYpjNSpt cDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUanZJ1qCeu2HL5ugL2 17CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQIDAQABo04wTDAp BgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0TAQH/BAgw BgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAMbFLR135AXHl9VNsXXnW PZjAJhNigSKnEvgilegbSbcnewQ5uvzm8iTrkfq97A0qOPdQVahs9w2tTBu8A/S166JHn2yi DFiNMUIJEWywGmnRKxKyQF1q+XnQ6i4l3Yrk/NsNH50C81rbyjz2ROomaYd/SJ7OpZ/nhNjJ YmKtBcYxggH1MIIB8QIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4g Q2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENl cnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAw MC44LjMwAgMIUvEwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG CSqGSIb3DQEJBTEPFw0wMzAxMTQxOTE4MTdaMCMGCSqGSIb3DQEJBDEWBBRPEs/44UG6pyf0 vp5gGBNpgwNUjzBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA gDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEF AASBgHEC8zInk2Y0C45SfEnMpD5S4KIlmJ+xGhj8Dey0g8R48z3b5kXSApIKA+Gyme/icbEJ SmXbS39LxjDNdDvkuty4Z4hJMZCwwHFwJdpCuc6BY1jFh/oDjadqmA46xicnbU0b3xj0oLBp /N+OdZOYuNhlkWQ0f8u3jF6/Czth7TCQ --------------ms117E192E22D0009838080896-- From woods@proven.weird.com Thu Jan 16 11:16:51 2003 Received: from most.weird.com (IDENT:/Tz2iq01xeFcVcw/YtPGVIv354arYz3scfsJtQ1DdTLwZF5bV8M1EsKH2UHWtGBuQoeRyFfB4Fc@most.weird.com [204.92.254.2]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0GJGool024560 for ; Thu, 16 Jan 2003 11:16:51 -0800 (PST) Received: from proven.weird.com([204.92.254.15]) (3673 bytes) by most.weird.com via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident <[a8wTD0y9MxdD3+PDDspdfAIe1vHguzjtjG+13n5KVoKQjj6GeT61qJ8qDgz+v7N81O5LDxTE6ZAx+HIJQCAN2Q==]> using rfc1413) id for ; Thu, 16 Jan 2003 14:16:48 -0500 (EST) (Smail-3.2.0.115-Pre 2001-Aug-6 #12 built 2003-Jan-14) Received: by proven.weird.com (Postfix, from userid 1000) id 4AE5FA; Thu, 16 Jan 2003 14:16:47 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: ;j3Eth2XV8h1Yfu*uL{<:dQ$#E[DB0gemGZJ"J#4fH*][ lz;@-iwMv_u\6uIEKR0KY"=MzoQH#CrqBN`nG_5B@rrM8,f~Gr&h5a\= To: Ernie Oporto Cc: users@conserver.com Subject: Re: How to tell Sun keyboard console from serial console? In-Reply-To: <3E246279.72EC9971@viragelogic.com> References: <3E246279.72EC9971@viragelogic.com> X-Mailer: VM 7.07 under Emacs 21.2.1 Reply-To: users@conserver.com (ConServer Users Mailing List) Organization: Planix, Inc.; Toronto, Ontario; Canada Message-Id: <20030116191647.4AE5FA@proven.weird.com> Date: Thu, 16 Jan 2003 14:16:47 -0500 (EST) Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: [ On Tuesday, January 14, 2003 at 14:18:17 (-0500), Ernie Oporto wrote: ] > Subject: How to tell Sun keyboard console from serial console? > > I there a way to tell whether a console is at the keyboard or at the > serial port on a Sun machine? The "tty" command gives /dev/console for > both. It depends somewhat on the particular type of machine and on the OS that you're running on it. Normally I believe on all modern versions of Solaris (SunOS-5) the /dev/console file is a symbolic link to the actual device file in the /devices directory. On most/many/all versions and variants of Unix since the very beginning the console device is a pseudo device that's mapped inside the kernel to whatever real device(s) are configured or probed to be the physical console. As you'll read in the console(7D) manual page: DESCRIPTION The file /dev/console refers to the system console device. SPARC The identity of this device depends on the EEPROM or NVRAM settings in effect at the most recent system reboot; by default, it is the ``workstation console'' device consisting of the workstation keyboard and frame buffer acting in con- cert to emulate an ASCII terminal (see wscons(7D)). With Solaris 9 on a SunFire V100 I could find no particular hint in the 'dmesg' output suggesting how the console is attached. On NetBSD it's pretty easy to see (especially if you also know what the zs1 and zs0 devices are): $ /sbin/dmesg | fgrep console kbd0 at zs1 channel 0 (console input) bwtwo0 at sbus0 slot 2 offset 0x0 level 9: SUNW,501-1419, 1600 x 1280 (console) $ /sbin/dmesg | fgrep console zstty0 at zs0 channel 0 (console i/o) You can also query the EEPROM/NVRAM settings on NetBSD and on Solaris: On NetBSD: # eeprom 2>/dev/null | fgrep put-device= output-device=ttya input-device=ttya # eeprom 2>/dev/null | fgrep put-device= output-device=screen input-device=keyboard On SunOS: $ /usr/platform/`uname -i`/sbin/eeprom | fgrep put-device= output-device=screen input-device=keyboard I'm not sure which information source you should trust more on Solaris, but on NetBSD it's definitely the 'dmesg' output that's authoritative. -- Greg A. Woods +1 416 218-0098; ; Planix, Inc. ; VE3TCP; Secrets of the Weird From mtdolan@twinight.org Sun Jan 19 16:18:09 2003 Received: from dawn.twinight.org (IDENT:postfix@dawn.twinight.org [65.39.69.132]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0K0I8ol012431 for ; Sun, 19 Jan 2003 16:18:08 -0800 (PST) Received: by dawn.twinight.org (Postfix, from userid 2016) id F199E4AE0; Sun, 19 Jan 2003 19:18:06 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by dawn.twinight.org (Postfix) with SMTP id E2DE62E2C0 for ; Sun, 19 Jan 2003 19:18:06 -0500 (EST) Date: Sun, 19 Jan 2003 19:18:06 -0500 (EST) From: Michael Dolan To: users@conserver.com Subject: Re: How to tell Sun keyboard console from serial console? In-Reply-To: <3E246279.72EC9971@viragelogic.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/SIGNED; PROTOCOL="application/x-pkcs7-signature"; MICALG=sha1; BOUNDARY=------------ms117E192E22D0009838080896 Content-ID: Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --------------ms117E192E22D0009838080896 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-ID: As long as the kbd was not attached at time of power-on, then console is not the framebuffer. If a kbd was attached at power and a /dev/fb exists, console will be framebuffer unless eeprom is set specifically to ttya (or rsc). Although its probably logged somewhere, the info in that logfile might be stale or overwritten. You can determine if the console is the framebuffer or not with: "prtconf -F". Excerpt from manpage: -F (SPARC only). Returns the device path name of the con- sole frame buffer, if one exists. If there is no frame buffer, prtconf returns a non-zero exit code. This flag must be used by itself. It returns only the name of the console, frame buffer device or a non-zero exit code. For example, if the console frame buffer on a SPARCstation 1 is cgthree in SBus slot #3, the command returns: /sbus@1,f80000000/cgthree@3,0. This option could be used to create a symlink for /dev/fb to the actual console device. examples: :Ultra80 workstation (kbd/fb attached) ultra80(2)% prtconf -F /SUNW,afb@1e,0:afb0 :Ultra5 "server". No kbd but has onboard PGX. ultra5(1)% prtconf -F Console output device is not a frame buffer :NetraT1 netra-t1-105(1)% prtconf -F Console output device is not a frame buffer --------------ms117E192E22D0009838080896-- From woods@proven.weird.com Sun Jan 19 16:33:05 2003 Received: from most.weird.com (IDENT:TMNGYG85PgCLdhWom3Sf5sxhbgrm+qlFzCR8tt07DEALoOcIj59PtsWjqETUSpH8+du9NaQfXyk@mail.weird.com [204.92.254.2]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0K0X4ol012578 for ; Sun, 19 Jan 2003 16:33:04 -0800 (PST) Received: from proven.weird.com([204.92.254.15]) (2535 bytes) by most.weird.com via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident <[NdOlIoCBokM/CK1tVCDS+XhPBXyaEVnzZNdkr6cXOgB/WGfvBksNaORDg6drScETkJA8ldZWaQ0SdqXxIDRDtw==]> using rfc1413) id for ; Sun, 19 Jan 2003 19:33:02 -0500 (EST) (Smail-3.2.0.115-Pre 2001-Aug-6 #1 built 2003-Jan-16) Received: by proven.weird.com (Postfix, from userid 1000) id 57AECA; Sun, 19 Jan 2003 19:32:57 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: ;j3Eth2XV8h1Yfu*uL{<:dQ$#E[DB0gemGZJ"J#4fH*][ lz;@-iwMv_u\6uIEKR0KY"=MzoQH#CrqBN`nG_5B@rrM8,f~Gr&h5a\= To: Michael Dolan Cc: users@conserver.com (ConServer Users Mailing List) Subject: Re: How to tell Sun keyboard console from serial console? In-Reply-To: References: <3E246279.72EC9971@viragelogic.com> X-Mailer: VM 7.07 under Emacs 21.2.1 Reply-To: users@conserver.com (ConServer Users Mailing List) Organization: Planix, Inc.; Toronto, Ontario; Canada Message-Id: <20030120003257.57AECA@proven.weird.com> Date: Sun, 19 Jan 2003 19:32:57 -0500 (EST) Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: [ On Sunday, January 19, 2003 at 19:18:06 (-0500), Michael Dolan wrote: ] > Subject: Re: How to tell Sun keyboard console from serial console? > > As long as the kbd was not attached at time of power-on, then console is > not the framebuffer. Substitute /power-on/ for /boot/ and you're probably right. > If a kbd was attached at power and a /dev/fb exists, > console will be framebuffer unless eeprom is set specifically to ttya (or rsc). I'm pretty sure it does not matter whether the file or linkg "/dev/fb" exists or not, but otherwise I think that's essentially true. > Although its probably logged somewhere, the info in that logfile might be > stale or overwritten. You can determine if the console is the framebuffer > or not with: "prtconf -F". I'm not sure that's the same as knowing whether the kernel thinks it's "console" pseudo-device is attached to the KBD & FB or not, and I wouldn't want to bet on it without seeing the source.... :-) -- Greg A. Woods +1 416 218-0098; ; Planix, Inc. ; VE3TCP; Secrets of the Weird From mtdolan@twinight.org Mon Jan 20 14:55:14 2003 Received: from dawn.twinight.org (IDENT:postfix@dawn.twinight.org [65.39.69.132]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0KMtDol026695 for ; Mon, 20 Jan 2003 14:55:14 -0800 (PST) Received: by dawn.twinight.org (Postfix, from userid 2016) id 802944ADC; Mon, 20 Jan 2003 17:55:13 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by dawn.twinight.org (Postfix) with SMTP id 60DA42E2A7 for ; Mon, 20 Jan 2003 17:55:13 -0500 (EST) Date: Mon, 20 Jan 2003 17:55:12 -0500 (EST) From: Michael Dolan Reply-To: Michael Dolan To: ConServer Users Mailing List Subject: Re: How to tell Sun keyboard console from serial console? In-Reply-To: <20030120003257.57AECA@proven.weird.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: On Sun, 19 Jan 2003, Greg A. Woods wrote: > Date: Sun, 19 Jan 2003 19:32:57 -0500 (EST) > Substitute /power-on/ for /boot/ and you're probably right. True. If you reboot/reset from a workstation console and pull the kbd in time... :) > I'm not sure that's the same as knowing whether the kernel thinks it's > "console" pseudo-device is attached to the KBD & FB or not, and I > wouldn't want to bet on it without seeing the source.... :-) I think "prtconf -F" will suffice for most queries, but if you want to be sure, try this... clumbsy but functional, and you might not want to do it in absolute mission critical environments during production hours: # adb -k /dev/ksyms /dev/mem wscons/D wscons: 1 (workstation console, ie kbd/fb) or wscons: 0 (ttya, ttyb, rsc, other?) I tested this under solaris7 - 9 on various workstations with kbd/fb and servers w/o, including E10K and SFx800, results were consistent. See wscons(7d) for more info. It might be useful (or not) to point out that you can ensure console output is always ttya by setting eeprom variables to such. (Caveat being E10K, SFx800, and RSC consoles). You can serial consoles on graphical workstations by setting the eeprom variables to ttya, ttyb or rsc and modify your Xservers file (replace 'console' with 'none' for :0). In addition, the consadm (1m) facility (s7 and higher?) adds support for auxilary consoles. Besides the default console, you can add additional consoles for output (and input up through single-user mode). You can add a second console to a running system and attach to it read-only. Tangent: I suppose one could build a redundant serial console solution by having duplicate conservers and serial concentrators/cabling setups, one attaches consoles to ttya and one attaches to ttyb. In a fashion, Console-HA... for that occasion when you fry a serial port or trash your primary console infrastructure. Overkill for most environments. :) -dolan From nicholas@penney.name Tue Jan 21 07:46:03 2003 Received: from wellington.csi.net.uk (wellington.csi.net.uk [212.15.64.10]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0LFk1ol007996 for ; Tue, 21 Jan 2003 07:46:02 -0800 (PST) Received: from postaccess.com ([212.15.85.11]) by wellington.csi.net.uk (8.10.2/8.10.2) with ESMTP id h0LFjCv11609 for ; Tue, 21 Jan 2003 15:45:12 GMT Received: from ravms by postaccess.com with mail-ok (Exim 3.36 #3) id 18b2Z4-0005FR-00 for users@conserver.com; Tue, 21 Jan 2003 17:51:58 +0000 Received: from cls8 ([127.0.0.1] helo=postaccess.com) by postaccess.com with asmtp (Exim 3.36 #3) id 18b2Z3-0005FI-00 for users@conserver.com; Tue, 21 Jan 2003 17:51:57 +0000 Received: from 194.128.222.17 (SquirrelMail authenticated user nicholas.penney@postaccess.com) by mail.postaccess.com with HTTP; Tue, 21 Jan 2003 17:51:57 -0000 (GMT) Message-ID: <41369.194.128.222.17.1043171517.squirrel@mail.postaccess.com> Date: Tue, 21 Jan 2003 17:51:57 -0000 (GMT) Subject: Conserver + RSC ports? From: "Nicholas Penney" To: X-Priority: 3 Importance: Normal Reply-To: nicholas@penney.name X-Mailer: SquirrelMail (version 1.2.8) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Envelope-To: users@conserver.com Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: I am currently running conserver version 7.2.2 utilising several Perle CS9000's for a whole bunch of assorted Sun servers. I was wondering if anyone has successfully set up conserver to use the RSC ports thta are available on newer sun harware (such as V800's)? If so, could you give me an example on how to set this up from your conserver.cf file? -- Nicholas Penney @ Home From trevor@seven.com Wed Jan 22 13:34:54 2003 Received: from rwc-ex0.corp.seven.com ([209.19.98.171]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0MLYsol025400 for ; Wed, 22 Jan 2003 13:34:54 -0800 (PST) Received: from seven.com ([10.0.36.33]) by rwc-ex0.corp.seven.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 22 Jan 2003 13:37:38 -0800 Message-ID: <3E2F0E6F.4020501@seven.com> Date: Wed, 22 Jan 2003 13:34:39 -0800 From: Trevor Fiatal User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: nicholas@penney.name CC: users@conserver.com Subject: Re: Conserver + RSC ports? References: <41369.194.128.222.17.1043171517.squirrel@mail.postaccess.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 22 Jan 2003 21:37:38.0140 (UTC) FILETIME=[7BE959C0:01C2C25E] Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Nicholas Penney wrote: > I am currently running conserver version 7.2.2 utilising several Perle > CS9000's for a whole bunch of assorted Sun servers. > > I was wondering if anyone has successfully set up conserver to use the RSC > ports thta are available on newer sun harware (such as V800's)? If so, > could you give me an example on how to set this up from your conserver.cf > file? We are using conserver to manage the serial ports on our RSC cards, but we're not doing anything particularly interesting with them. We treat them as regular console ports, attached to Cisco 32-port async serial cards in 2600/3600 chassis. It would be nice if we had a script which would automatically log in to the RSC card and switch to the redirected console connection, but it hasn't been enough of an annoyance to actually automate the process. Were you, perhaps, referring to the use of conserver to manage each RSC card like a single-port console server, via telnet? -Trevor -- Trevor Fiatal -- trevor@seven.com -- http://www.seven.com/ Co-Founder, CSO SEVEN 650.862.3715 (work/mobile) From nicholas@penney.name Thu Jan 23 03:14:57 2003 Received: from alderney.csi.net.uk (alderney.csi.net.uk [212.15.64.30]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0NBEtol005238 for ; Thu, 23 Jan 2003 03:14:56 -0800 (PST) Received: from postaccess.com ([212.15.85.11]) by alderney.csi.net.uk (8.10.2/8.10.2) with ESMTP id h0NBJ4e12595 for ; Thu, 23 Jan 2003 11:19:05 GMT Received: from ravms by postaccess.com with mail-ok (Exim 3.36 #3) id 18bhHx-0005iw-00 for users@conserver.com; Thu, 23 Jan 2003 13:21:01 +0000 Received: from cls8 ([127.0.0.1] helo=postaccess.com) by postaccess.com with asmtp (Exim 3.36 #3) id 18bhHv-0005ig-00; Thu, 23 Jan 2003 13:20:59 +0000 Received: from 194.72.41.179 (SquirrelMail authenticated user nicholas.penney@postaccess.com) by mail.postaccess.com with HTTP; Thu, 23 Jan 2003 13:20:59 -0000 (GMT) Message-ID: <36490.194.72.41.179.1043328059.squirrel@mail.postaccess.com> Date: Thu, 23 Jan 2003 13:20:59 -0000 (GMT) Subject: Re: Conserver + RSC ports? From: "Nicholas Penney" To: In-Reply-To: <3E2F0E6F.4020501@seven.com> References: <41369.194.128.222.17.1043171517.squirrel@mail.postaccess.com> <3E2F0E6F.4020501@seven.com> X-Priority: 3 Importance: Normal Cc: Reply-To: nicholas@penney.name X-Mailer: SquirrelMail (version 1.2.8) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Envelope-To: trevor@seven.com, users@conserver.com, nicholas@penney.name Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Trevor, Yes, I would really like to be able to use conserver to connect to the RSC, using telnet or ssh, and drop me directly to the console prompt. Can you show me an example of one of your conserver config lines from a host using and RSC (changing any names etc. as necessary)? Trevor Fiatal said: > Nicholas Penney wrote: >> I am currently running conserver version 7.2.2 utilising several Perle >> CS9000's for a whole bunch of assorted Sun servers. >> >> I was wondering if anyone has successfully set up conserver to use the >> RSC ports thta are available on newer sun harware (such as V800's)? >> If so, could you give me an example on how to set this up from your >> conserver.cf file? > > We are using conserver to manage the serial ports on our RSC cards, but > we're not doing anything particularly interesting with them. We treat > them as regular console ports, attached to Cisco 32-port async serial > cards in 2600/3600 chassis. It would be nice if we had a script which > would automatically log in to the RSC card and switch to the redirected > console connection, but it hasn't been enough of an annoyance to > actually automate the process. > > Were you, perhaps, referring to the use of conserver to manage each RSC > card like a single-port console server, via telnet? > > -Trevor > > > -- > Trevor Fiatal -- trevor@seven.com -- http://www.seven.com/ > Co-Founder, CSO > SEVEN > 650.862.3715 (work/mobile) -- Nicholas Penney @ Home Tel: 07005 942 941 Fax: 07005 968 641 Those of you who think you know everything are annoying those of us who do. From cfowler@outpostsentinel.com Thu Jan 23 05:04:40 2003 Received: from cfowler.outpostsentinel.com (dsl-64-129-133-253.telocity.com [64.129.133.253]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0ND4dol006129 for ; Thu, 23 Jan 2003 05:04:39 -0800 (PST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id h0ND7Ax01911; Thu, 23 Jan 2003 08:07:10 -0500 Subject: Re: Conserver + RSC ports? From: cfowler To: nicholas@penney.name Cc: trevor@seven.com, users@conserver.com In-Reply-To: <36490.194.72.41.179.1043328059.squirrel@mail.postaccess.com> References: <41369.194.128.222.17.1043171517.squirrel@mail.postaccess.com> <3E2F0E6F.4020501@seven.com> <36490.194.72.41.179.1043328059.squirrel@mail.postaccess.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 23 Jan 2003 08:07:10 -0500 Message-Id: <1043327231.1873.0.camel@cfowler.outpostsentinel.com> Mime-Version: 1.0 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Do the RSC ports support OpenSSL via SSH? My experience shows it as being old-fashioned plain-text. On Thu, 2003-01-23 at 08:20, Nicholas Penney wrote: > Trevor, > > Yes, I would really like to be able to use conserver to connect to the > RSC, using telnet or ssh, and drop me directly to the console prompt. > > Can you show me an example of one of your conserver config lines from a > host using and RSC (changing any names etc. as necessary)? > > Trevor Fiatal said: > > Nicholas Penney wrote: > >> I am currently running conserver version 7.2.2 utilising several Perle > >> CS9000's for a whole bunch of assorted Sun servers. > >> > >> I was wondering if anyone has successfully set up conserver to use the > >> RSC ports thta are available on newer sun harware (such as V800's)? > >> If so, could you give me an example on how to set this up from your > >> conserver.cf file? > > > > We are using conserver to manage the serial ports on our RSC cards, but > > we're not doing anything particularly interesting with them. We treat > > them as regular console ports, attached to Cisco 32-port async serial > > cards in 2600/3600 chassis. It would be nice if we had a script which > > would automatically log in to the RSC card and switch to the redirected > > console connection, but it hasn't been enough of an annoyance to > > actually automate the process. > > > > Were you, perhaps, referring to the use of conserver to manage each RSC > > card like a single-port console server, via telnet? > > > > -Trevor > > > > > > -- > > Trevor Fiatal -- trevor@seven.com -- http://www.seven.com/ > > Co-Founder, CSO > > SEVEN > > 650.862.3715 (work/mobile) > > > -- > Nicholas Penney @ Home > Tel: 07005 942 941 Fax: 07005 968 641 > Those of you who think you know everything are annoying those of us who do. > > > > _______________________________________________ > users mailing list > users@conserver.com > https://www.conserver.com/mailman/listinfo/users From trevor@seven.com Thu Jan 23 15:02:01 2003 Received: from rwc-ex0.corp.seven.com ([209.19.98.171]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0NN20ol010872 for ; Thu, 23 Jan 2003 15:02:01 -0800 (PST) Received: from seven.com ([10.0.36.33]) by rwc-ex0.corp.seven.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 23 Jan 2003 15:04:52 -0800 Message-ID: <3E307514.3070203@seven.com> Date: Thu, 23 Jan 2003 15:04:52 -0800 From: Trevor Fiatal User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: nicholas@penney.name CC: trevor@seven.com, users@conserver.com Subject: Re: Conserver + RSC ports? References: <41369.194.128.222.17.1043171517.squirrel@mail.postaccess.com> <3E2F0E6F.4020501@seven.com> <36490.194.72.41.179.1043328059.squirrel@mail.postaccess.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Jan 2003 23:04:52.0234 (UTC) FILETIME=[D61676A0:01C2C333] Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Nicholas Penney wrote: > Trevor, > > Yes, I would really like to be able to use conserver to connect to the > RSC, using telnet or ssh, and drop me directly to the console prompt. > > Can you show me an example of one of your conserver config lines from a > host using and RSC (changing any names etc. as necessary)? As I mentioned, we don't currently use an autologin script to log in to the RSC port and drop to the console. Instead, our standard operating procedure is to log in to the RSC any time we find one not already in 'console pass-through' mode, and leave in console mode when we log out. (The alternative would be to embed a RSC login ID and password into a script used by conserver, and I am not in favor of storing usernames and passwords in scripts.) Here's an example of how you might set up conserver to directly access your RSC cards instead of a terminal server hooked up to ttya. Note that 'hostname-RSC' should resolve to the IP address for the conserver card in the server, either via /etc/hosts or in DNS. 'conserver0' is the name of the primary conserver host managing your consoles. hostname:!hostname-RSC@conserver0:23:&.log:10m Hope this helps. -Trevor -- Trevor Fiatal -- trevor@seven.com -- http://www.seven.com/ Co-Founder, CSO SEVEN 650.862.3715 (work/mobile) From bryan@stansell.org Mon Jan 27 17:59:22 2003 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0S1xMol013187; Mon, 27 Jan 2003 17:59:22 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.7/8.12.7/Submit) id h0S1xM60013186; Mon, 27 Jan 2003 17:59:22 -0800 (PST) Date: Mon, 27 Jan 2003 17:59:22 -0800 From: Bryan Stansell To: users@conserver.com, announce@conserver.com Subject: conserver 7.2.5 is available Message-ID: <20030128015921.GA13072@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: This release adds a couple of new features and cleans up a few things. Hopefully some of the new features will be useful (especially SIGUSR2). Here are all the changes: version 7.2.5 (Jan 27, 2003): - fixed many documentation bugs - reported by Dave Stuit - added -I option to client which operates like -i, but on the primary conserver only - suggested by Dave Stuit - added SIGUSR2, which does not reread the configuration file, but does everything else SIGHUP does - suggested at LISA 2002 - fixed bug where LOGDIR setting gets used even if no logfile is wanted - added -R option to server to prevent client redirection to other conserver hosts - suggested by Todd Stansell Bryan Stansell From sia@seagull.nest.org Mon Jan 27 21:40:56 2003 Received: from seagull.nest.org (IDENT:Cg4WzIRYyXocHplsodlhzrMTgAhBRUtn@seagull.nest.org [209.66.103.72]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0S5etol014875 for ; Mon, 27 Jan 2003 21:40:55 -0800 (PST) Received: (from sia@localhost) by seagull.nest.org (8.8.8/8.8.8/KOLO.NET-SINK-V1.3) id VAA18510 for users@conserver.com; Mon, 27 Jan 2003 21:40:56 -0800 (PST) (envelope-from sia) Date: Mon, 27 Jan 2003 21:40:56 -0800 From: Igor Sviridov To: users@conserver.com Subject: problem with "conserver -M bindaddress" and proposed patch Message-ID: <20030127214056.F13432@seagull.nest.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="W/nzBZO5zC0uMSeA" X-Mailer: Mutt 0.95i Precedence: special-delivery X-Class: Fast X-NIC-Handle: IS39 X-Home-Email: sia@nest.org X-Home-Snail: 650 Castro St, Ste 120-335, Mountain View, CA 94041 X-Home-Talk: sia@seagull.nest.org X-Pager-Email: sia@sms.nest.org X-Voicemail: +1 877 5705414 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii hi, if "-M bindaddress" is used conserver would encounter problem under the following circumstances: - @servername syntax is used in conserver.cf - gethostname differs from -M bindaddress for example if you're running conserver on internal interface but system default hostname points to external interface; if you use internal hostname (!= main) in @servername local conserver would be unable to match @servername to itself and assume those consoles are remote; you can't use external name since conserver is bound to another interface and remote clients may not be able to connect. the trivial fix is to override own IP with bindaddress; it's not used anywhere else (except setting up default ACL) as far as i can tell: patch against 7.2.4 is attached. --igor --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-main.c" --- conserver/main.c.orig Sat Oct 12 20:07:50 2002 +++ conserver/main.c Mon Jan 27 19:29:01 2003 @@ -888,6 +888,7 @@ Error("inet_addr: %s: %s", pcAddress, "invalid IP address"); exit(EX_UNAVAILABLE); } + acMyAddr.s_addr = bindAddr; } if (fDebug) { struct in_addr ba; --W/nzBZO5zC0uMSeA-- From cfowler@outpostsentinel.com Fri Jan 31 06:35:55 2003 Received: from cfowler.outpostsentinel.com (66-23-198-138.clients.speedfactory.net [66.23.198.138]) by underdog.stansell.org (8.12.7/8.12.7) with ESMTP id h0VEZrol006558 for ; Fri, 31 Jan 2003 06:35:54 -0800 (PST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by cfowler.outpostsentinel.com (8.11.6/8.11.6) with ESMTP id h0VEZa208033 for ; Fri, 31 Jan 2003 09:35:37 -0500 Subject: Automatic intilization From: cfowler To: users@conserver.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 31 Jan 2003 09:35:36 -0500 Message-Id: <1044023737.30426.22.camel@cfowler.outpostsentinel.com> Mime-Version: 1.0 Sender: users-admin@conserver.com Errors-To: users-admin@conserver.com X-BeenThere: users@conserver.com X-Mailman-Version: 2.0.13 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: If a network connection goes down then conserver loops trying to make that connection again. IT seems like it does it really fast 5 times or so in a row. If 10 minutes later, I bring up that remote, does conserver reinitlize or do I have to do something first?