From AMorris@providence.org Fri Feb 1 09:36:49 2002 Received: from phsorcon02.phsor.org ([170.220.2.13]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g11Ham2S017732 for ; Fri, 1 Feb 2002 09:36:48 -0800 (PST) Received: by phsorcon02.phsor.org with Internet Mail Service (5.5.2653.19) id ; Fri, 1 Feb 2002 09:36:43 -0800 Message-ID: From: "Morris, Adam" To: users@conserver.com Subject: Compilation on HP-UX 11i using GCC 3.02 Date: Fri, 1 Feb 2002 09:36:18 -0800 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: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Greetings, I have sent a patch to Bryan detailing all of the changes that I made. I'm not up to speed on GNU Autoconf so I skipped integrating my changes with the ./configure stuff. However, I've got it compiling problem free and working properly as well (minor problem in access.c). Conserver 7.1.4 is now working properly on HP-UX 11i for me. If anyone needs/wants the patch before it's merged, please let me know. Many thanks to Bryan for all of his work on Conserver. Adam. **************************************************************************** This message is intended for the sole use of the individual and entity to whom it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you very much. From CGobbo@carnival.com Fri Feb 8 09:01:08 2002 Received: from dmz-dns2.carnival.com (smtp2.carnival.com [151.124.250.202]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g18H172S021984 for ; Fri, 8 Feb 2002 09:01:07 -0800 (PST) Received: from cclbridge2.carnival.com (cclbridge2.carnival.com [172.25.171.34]) by dmz-dns2.carnival.com (8.9.3/8.9.3) with SMTP id MAA09764 for ; Fri, 8 Feb 2002 12:07:22 -0500 (EST) Received: FROM cclbridge2.carnival.com BY cclbridge2.carnival.com ; Fri Feb 08 12:00:54 2002 -0500 Received: by mailhost.carnival.com with Internet Mail Service (5.5.2653.19) id <1N7S6KMF>; Fri, 8 Feb 2002 12:00:53 -0500 Message-ID: From: "Gobbo, Carl (CCL)" To: users@conserver.com Subject: Sun RSC console Date: Fri, 8 Feb 2002 12:00:51 -0500 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: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Currently I have configured a few portmasters connected to our serial ports with conserver controlling our consoles. We have been recently expanding and upgrading to Sun 280R systems in our Data Center. They all come with the RSC port that allows remote console access. I like the added features of the RSC port over serial, but I don't like how it logs. I would also like to keep a consistent face on how to connect to all of our servers. Rather then connecting up more servers to the portmaster (we are almost at the point of needing yet another one), I would like to let conserver use the RSC network port. Does anyone have some of these configurations? Carl ---- Carl Gobbo Unix System Administrator Carnival Cruise Lines From trevor@seven.com Sun Feb 10 01:21:36 2002 Received: from raptor.seven.com (raptor.dmz.seven.com [209.19.68.204]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1A9La2S020866 for ; Sun, 10 Feb 2002 01:21:36 -0800 (PST) Received: from seven.com ([10.0.4.111]) by raptor.seven.com with ESMTP id <20020210092130.CSAK1431.raptor@seven.com>; Sun, 10 Feb 2002 01:21:30 -0800 Message-ID: <3C663C01.B2FA61A3@seven.com> Date: Sun, 10 Feb 2002 01:23:13 -0800 From: Trevor Fiatal Organization: SEVEN X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Gobbo, Carl (CCL)" CC: users@conserver.com Subject: Re: Sun RSC console References: Content-Type: text/plain; charset=us-ascii 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.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: "Gobbo, Carl (CCL)" wrote: > > Currently I have configured a few portmasters connected to our serial ports > with conserver controlling our consoles. We have been recently expanding > and upgrading to Sun 280R systems in our Data Center. They all come with > the RSC port that allows remote console access. I like the added features > of the RSC port over serial, but I don't like how it logs. I would also > like to keep a consistent face on how to connect to all of our servers. > > Rather then connecting up more servers to the portmaster (we are almost at > the point of needing yet another one), I would like to let conserver use the > RSC network port. Does anyone have some of these configurations? This one is remarkably easy, actually. If you think of the RSC card as a single-port terminal server on tcp/23, you get something like this in your config file: somehost:!somehost-rsc@conserver-host:23:&.log:10m You need a DNS entry for 'somehost-rsc' mapping to the IP of the RSC card. Everything else should be obvious. Hope this helps. -Trevor -- Trevor Fiatal -- trevor@seven.com -- http://www.seven.com/ Co-Founder, CSO SEVEN 650.862.3715 (work/mobile) <-- Note new number! 510.401.8054 (vmail/fax) From CGobbo@carnival.com Tue Feb 12 05:08:27 2002 Received: from dmz-dns1.carnival.com (smtp1.carnival.com [151.124.250.201]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1CD8Q2S021789 for ; Tue, 12 Feb 2002 05:08:26 -0800 (PST) Received: from cclbridge1.carnival.com (cclbridge1.carnival.com [172.25.161.36]) by dmz-dns1.carnival.com (8.9.3/8.9.3) with SMTP id IAA18536 for ; Tue, 12 Feb 2002 08:08:43 -0500 (EST) Received: FROM cclbridge1.carnival.com BY cclbridge1.carnival.com ; Tue Feb 12 08:08:24 2002 -0500 Received: by mailhost.carnival.com with Internet Mail Service (5.5.2653.19) id <1N54H6V8>; Tue, 12 Feb 2002 08:08:24 -0500 Message-ID: From: "Gobbo, Carl (CCL)" To: "'Trevor Fiatal'" , "Gobbo, Carl (CCL)" Cc: users@conserver.com Subject: RE: Sun RSC console Date: Tue, 12 Feb 2002 08:08:20 -0500 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: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: But you would need to have a login and password for the RSC port. Then pass the commands for console. I just have to find the time to write a script that will connect and pass the correct commands to the rsc. Example: telnet somehost-rsc Connected to somehost-rsc Escape character is '^]'. RSC version 2.1 (somehost-rsc) Please login: conuser Please Enter password: rsc> console Carl -----Original Message----- From: Trevor Fiatal [mailto:trevor@seven.com] Sent: Sunday, February 10, 2002 4:23 AM To: Gobbo, Carl (CCL) Cc: users@conserver.com Subject: Re: Sun RSC console "Gobbo, Carl (CCL)" wrote: > > Currently I have configured a few portmasters connected to our serial ports > with conserver controlling our consoles. We have been recently expanding > and upgrading to Sun 280R systems in our Data Center. They all come with > the RSC port that allows remote console access. I like the added features > of the RSC port over serial, but I don't like how it logs. I would also > like to keep a consistent face on how to connect to all of our servers. > > Rather then connecting up more servers to the portmaster (we are almost at > the point of needing yet another one), I would like to let conserver use the > RSC network port. Does anyone have some of these configurations? This one is remarkably easy, actually. If you think of the RSC card as a single-port terminal server on tcp/23, you get something like this in your config file: somehost:!somehost-rsc@conserver-host:23:&.log:10m You need a DNS entry for 'somehost-rsc' mapping to the IP of the RSC card. Everything else should be obvious. Hope this helps. -Trevor -- Trevor Fiatal -- trevor@seven.com -- http://www.seven.com/ Co-Founder, CSO SEVEN 650.862.3715 (work/mobile) <-- Note new number! 510.401.8054 (vmail/fax) From trevor@seven.com Tue Feb 12 09:30:45 2002 Received: from raptor.seven.com (raptor.dmz.seven.com [209.19.68.204]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1CHUi2S023797 for ; Tue, 12 Feb 2002 09:30:44 -0800 (PST) Received: from seven.com ([10.0.4.123]) by raptor.seven.com with ESMTP id <20020212173039.DAHS1431.raptor@seven.com>; Tue, 12 Feb 2002 09:30:39 -0800 Message-ID: <3C6951A6.BE79D5C5@seven.com> Date: Tue, 12 Feb 2002 09:32:22 -0800 From: Trevor Fiatal Organization: SEVEN X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Gobbo, Carl (CCL)" CC: users@conserver.com Subject: Re: Sun RSC console References: Content-Type: text/plain; charset=us-ascii 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.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: "Gobbo, Carl (CCL)" wrote: > > But you would need to have a login and password for the RSC port. Then pass > the commands for console. I just have to find the time to write a script > that will connect and pass the correct commands to the rsc. > > Example: > telnet somehost-rsc > Connected to somehost-rsc > Escape character is '^]'. > > RSC version 2.1 (somehost-rsc) > > Please login: conuser > Please Enter password: > > rsc> console That'd be more elegant than my solution, I suppose. We just create a low-privileged RSC user and leave it logged in and set to 'console' mode. It's pretty rare that the low-privilege user would get logged out or escaped back to the RSC, so this isn't a hassle at all. -T. -- Trevor Fiatal -- trevor@seven.com -- http://www.seven.com/ Co-Founder, CSO SEVEN 650.862.3715 (work/mobile) <-- Note new number! 510.401.8054 (vmail/fax) From bryan@stansell.org Mon Feb 25 14:33:39 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1PMXc2S016473; Mon, 25 Feb 2002 14:33:38 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.2/8.12.2/Submit) id g1PMXcoc016472; Mon, 25 Feb 2002 14:33:38 -0800 (PST) Date: Mon, 25 Feb 2002 14:33:38 -0800 From: Bryan Stansell To: announce@conserver.com, users@conserver.com Subject: conserver-7.2.0-beta3 available (you'll really want this!) Message-ID: <20020225143338.D1141@underdog.stansell.org> 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: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Well folks, it's finally here. No more full restarts of conserver just because you want to edit the config file! I've personally been wanting this since I started maintaining the code (about seven years ago!). Now beta3 has the code required to do a full reconfiguration when you send a HUP signal to the server. Consoles that are removed (along with their clients) get dropped, new consoles are added (managed by forking off a new children), and changes to existing consoles are made with only a possible console reset (by bringing it down and back up - all clients stay connected). The one exception to that last rule is that if the console is managed by a new server, any existing clients have to get bumped off. All of this is done by tracking the console name, so if you are renaming a console, it's like removing and adding a new one. That last bit is unfortunate, but the console name is the center of everything and doing anything else just seemed like trouble. As before, you can find the code at http://www.conserver.com/beta/ or on the ftp server in the beta subdirectory. I must thank Dave Stuit of GNAC for all his help and patience. He tested many versions of this beta release, found many bugs, and helped make this a *much* more stable release than it would have been. I can't say there aren't any more bugs to find, but I'm hoping it's limited to the bizarre edge cases. Bryan Stansell From bryan@stansell.org Mon Feb 25 16:19:55 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1Q0Jt2S020052; Mon, 25 Feb 2002 16:19:55 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.2/8.12.2/Submit) id g1Q0JsQj020051; Mon, 25 Feb 2002 16:19:54 -0800 (PST) Date: Mon, 25 Feb 2002 16:19:54 -0800 From: Bryan Stansell To: announce@conserver.com, users@conserver.com Subject: conserver-7.2.0-beta3 is now there... Message-ID: <20020225161954.F1141@underdog.stansell.org> 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: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Well folks, I was a little trigger-happy again. If you tried to get the beta3 code and didn't succeed, try again now - it's there. I had pushed out the "bad beta3", basically. Then I found yet another bug that really needed fixing so I took the opportunity to fix it before pushing out the "good" version. Now to track down the one guy who got the bad code... :-( Bryan Stansell From slammert@panasas.com Tue Feb 26 12:45:33 2002 Received: from localhost.localdomain (gw2.panasas.com [65.194.124.178]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1QKjW2S003886 for ; Tue, 26 Feb 2002 12:45:33 -0800 (PST) Received: from panasas.com (palantir [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g1QKikw02782 for ; Tue, 26 Feb 2002 15:44:46 -0500 Message-ID: <3C7BF3BE.7090400@panasas.com> Date: Tue, 26 Feb 2002 15:44:46 -0500 From: Steve Lammert Organization: Panasas, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: users@conserver.com Subject: conserver and gdb 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.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: We have some developers who are working on kernel code, and wish to do their kernel debugging using GDB (the Gnu DeBugger). I am wondering whether anyone out there has made gdb work with conserver? Background: when debugging a UNIX kernel, the typical setup is to have two machines. The "master" is the one on which GDB is run. The "target" is the one on which the kernel-to-be-debugged is running. The target must have a serial console, which is normlly connected to a serial port on the master. GDB is then started on the master, and the command is given: (gdb) target remote /dev/ttyNN where /dev/ttyNN is the serial device on the master to which the serial cable from the target has been attached. With me so far? Now, it turns out that GDB also allows the target to be a remote terminal, e.g. a port on a terminal concentrator, in which case the syntax of the command looks like this: (gdb) target remote cyclades-1.mydomain.com:5007 In this case, the target's serial console is attached to port 7 of a Cyclades box, and GDB is more-or-less running a Telnet session under the covers to connect the master and the target. OK, here's the rub. When using Conserver to manage all of the serial ports on my Cyclades box, all of the ports are "busy" because Conserver is connected to all of them. But this prevents GDB from also attaching directly to the Cyclades port to establish a kernel debug session, using the second example above. I could modify conserver.cf to not manage any port on which I want to do kernel debugging, but that's a pain, especially when the host-to-be-debugged is constantly changing. It would be much nicer if gdb were Conserver-literate, and I could say something like (gdb) target conserver debug-host-7 But that would essentially require that GDB be modified to include pieces of the Conserver client code. Has anyone tried to do this? Or is there another way to handle this situation which (a) preserves Conserver access, and (b) doesn't involve a lot of manual manipulation on the part of the developer (or his admin)? Thanks, Steve L -- -- steve lammert test engineer voice: +1-412-323-3500 slammert@panasas.com panasas, inc. fax: +1-412-323-3511 From bryan@stansell.org Tue Feb 26 13:34:10 2002 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1QLYA2S004517 for ; Tue, 26 Feb 2002 13:34:10 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.12.2/8.12.2/Submit) id g1QLYAnb004516 for users@conserver.com; Tue, 26 Feb 2002 13:34:10 -0800 (PST) Date: Tue, 26 Feb 2002 13:34:10 -0800 From: Bryan Stansell To: users@conserver.com Subject: Re: conserver and gdb Message-ID: <20020226133410.J1141@underdog.stansell.org> References: <3C7BF3BE.7090400@panasas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C7BF3BE.7090400@panasas.com>; from slammert@panasas.com on Tue, Feb 26, 2002 at 03:44:46PM -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: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: hi steve, On Tue, Feb 26, 2002 at 03:44:46PM -0500, Steve Lammert wrote: > We have some developers who are working on kernel code, and wish to do > their kernel debugging using GDB (the Gnu DeBugger). I am wondering > whether anyone out there has made gdb work with conserver? great question! this should be good! > But that would essentially require that GDB be modified to include > pieces of the Conserver client code. yikes...wouldn't want to inflict that upon anyone. that's the one chunk of code i've been afraid to touch too much (although it might be next on my hit list). but, anyway... > Has anyone tried to do this? Or is there another way to handle this > situation which (a) preserves Conserver access, and (b) doesn't involve > a lot of manual manipulation on the part of the developer (or his admin)? let me ask a question and see if your philosophy changes at all. first let me say that i haven't used gdb in it's remote mode to do any debugging and haven't looked at what it expects. but, considering it's support is for a dedicated serial line or a tcp connection (which is normally dedicated), i can only assume it wouldn't want to see traffic that it wasn't expecting. so, the question is, is this true? how does this matter if you're using conserver's client code, you may ask? well... if gdb did have the client code and someone else forcefully took over the console, gdb would be bumped into spy mode and, i assume, get out of sync with the debugged kernel. you see, the fun part of the client-server code is that there is no knowledge on the client side of what's going on. it basically sets up a connection (through a series of interesting moves), logs in, and then blindly passes traffic back and forth (which, in my mind, is a nice feature, but has it's limitations). knowing when you're in spy mode, when the console is down, when others bump you - it's all done in the brain of the user. so, even if gdb had the client code, it wouldn't be able to know what state the console was in or how to recover without rewriting most of it to watch for special strings in the traffic (which is problematic at best). so, my initial reaction is to suggest that you "down" the console by connecting with the client and using the '^ecd' sequence. before you down it you could even type a nice little message for anyone else who connects and replays the last few lines. then, crank up gdb using the remote tcp port functionality (i'd keep the console client connection going just so you're the one in write mode and you see if someone else is trying to mess with the port). heck, you could also use '^ecx' to find out what the terminal server and port numbers should be (so you don't have to dig through the cf file). then, when you're done debugging the kernel, you disconnect gdb, use '^eco' to reconnect conserver, and move on. there's my initial thoughts on the whole thing. one of the "wishlist" items is to be able to redirect a command's i/o through the client. basically, you'd start up the client, connect, use a new sequence like '^ec|', give it a command, and it would fork the command off on the client, allowing it to chat with the console (and blocking others from bumping the command off). unfortunately, it's tricky (for a lot of the same reasons as above). but, i'm still thinking about if and how it could be done and that *might* be a future solution. but, that too has it's issues for gdb since stdin/stdout should still be the user interaction with gdb and some other pipe should be the interaction with gdb (i was thinking of just redirecting stdin/stdout of the command to the console). anyway, i hope something here helps and gives you a little insight into the inner-workings of the code. maybe with the info above you or someone can come up with a better solution than what i've suggested (or ideas for code changes). Bryan From woods@proven.weird.com Tue Feb 26 14:56:54 2002 Received: from most.weird.com (IDENT:+0xRt06MMQh7xE+f9Sss3tUcmI9qEU89ZWizvxDII1Gtkh2XSnFh/fcpLKRlGF5Kg7e0x3e+Me0@most.weird.com [204.92.254.2]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1QMur2S005172 for ; Tue, 26 Feb 2002 14:56:53 -0800 (PST) Received: from proven.weird.com([204.92.254.15]) (2551 bytes) by most.weird.com via smail with P:esmtp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident <[Sn27ESTbf5SXQNOAMgaF0rx+ndTUMK++fA5G2Z+ROykfwttdReB7+m4gqF7h4QN0sF5WB5F+UzaAwJUJMtSghg==]> using rfc1413) id for ; Tue, 26 Feb 2002 17:56:51 -0500 (EST) (Smail-3.2.0.115-Pre 2001-Aug-6 #39 built 2002-Feb-7) Received: by proven.weird.com (Postfix, from userid 1000) id B77CAB5; Tue, 26 Feb 2002 17:56:47 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: woods@weird.com (Greg A. Woods) To: users@conserver.com Subject: Re: conserver and gdb In-Reply-To: <20020226133410.J1141@underdog.stansell.org> References: <3C7BF3BE.7090400@panasas.com> <20020226133410.J1141@underdog.stansell.org> X-Mailer: VM 7.00 under Emacs 21.1.1 Reply-To: users@conserver.com Organization: Planix, Inc.; Toronto, Ontario; Canada Message-Id: <20020226225647.B77CAB5@proven.weird.com> Date: Tue, 26 Feb 2002 17:56:47 -0500 (EST) 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: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: [ On Tuesday, February 26, 2002 at 13:34:10 (-0800), Bryan Stansell wrote: ] > Subject: Re: conserver and gdb > > On Tue, Feb 26, 2002 at 03:44:46PM -0500, Steve Lammert wrote: > > > > But that would essentially require that GDB be modified to include > > pieces of the Conserver client code. > > yikes...wouldn't want to inflict that upon anyone. that's the one > chunk of code i've been afraid to touch too much (although it might be > next on my hit list). but, anyway... Hmm..... I was on the verge of asking for something similar for the nut-ups tools. I'd like to be able to gather stats from my conserver- connected UPS'. That was what originally prompted me to ask about reading and writing to a device through stdio of the "console" command. I sure as heck can't "down" the UPS consoles every minute or so just to collect the stats! ;-) Even if I couldn't read the result back from a pipeline to "console" I had contemplated just sending the command to the UPS that way and then collecting the result from the log file. For nut-ups and/or Cricket I could even separate the sending of the command and the collecting of the data. A cron job to do "echo f | console -f ups.1", and with timestamps in the log even Cricket can easily gather reliable stats with a not too complicated EXEC script. However like GDB, 'nut-ups' ideally needs more direct access to the UPS console for other purposes beyond stats collection. -- Greg A. Woods +1 416 218-0098; ; ; Planix, Inc. ; VE3TCP; Secrets of the Weird From slammert@panasas.com Tue Feb 26 16:00:39 2002 Received: from localhost.localdomain (gw2.panasas.com [65.194.124.178]) by underdog.stansell.org (8.12.2/8.12.2) with ESMTP id g1R00d2S005713; Tue, 26 Feb 2002 16:00:39 -0800 (PST) Received: from panasas.com (palantir [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id g1QNxpw03113; Tue, 26 Feb 2002 18:59:51 -0500 Message-ID: <3C7C2176.6050600@panasas.com> Date: Tue, 26 Feb 2002 18:59:50 -0500 From: Steve Lammert Organization: Panasas, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Bryan Stansell CC: users@conserver.com Subject: Re: conserver and gdb References: <3C7BF3BE.7090400@panasas.com> <20020226133410.J1141@underdog.stansell.org> 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.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: Bryan Stansell wrote: > ... > > if gdb did have the client code and someone else forcefully took over > the console, gdb would be bumped into spy mode and, i assume, get out > of sync with the debugged kernel... Um. Yes. That would be a Bad Thing. Of course, it would violate the Reasonable Person Principle for people to grab the console away. Users should "spy" first (and, happily, this is the default behavior when you connect to an in-use console) and only force RW mode when appropriate, and be soundly drubbed otherwise. But, down-ing the port would be an acceptable alternative, I think. Not as convenient for developers (they have to remember port numbers, or know how to look them up) and, for sure, they wouldn't remember to "up" them afterwards, so logs would get stale... but it's worth writing up a few paragraphs and getting some developers to give it a whirl. Thanks for the clear thinking on my problem, and for your other comments as well! -- -- steve lammert test engineer voice: +1-412-323-3500 slammert@panasas.com panasas, inc. fax: +1-412-323-3511 From zonker@certaintysolutions.com Tue Feb 26 16:18:08 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 g1R0I72S005936 for ; Tue, 26 Feb 2002 16:18:07 -0800 (PST) Received: by yosemite.rwc.gnac.net; id QAA20266; Tue, 26 Feb 2002 16:18:08 -0800 (PST) Received: from unknown(192.168.1.21) by yosemite.rwc.gnac.net via smap (V5.0) id xma020261; Tue, 26 Feb 02 16:18:04 -0800 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 g1R0Hhs16928 for ; Tue, 26 Feb 2002 16:17:43 -0800 (PST) Received: (from zonker@localhost) by tweety.main.gnac.com (8.9.3/8.7.3/GNAC-COM-1.1) id QAA07823 for users@conserver.com; Tue, 26 Feb 2002 16:18:02 -0800 (PST) Date: Tue, 26 Feb 2002 16:18:02 -0800 From: David Harris To: users@conserver.com Subject: shared access to console ports (was: conserver and gdb) Message-ID: <20020226161802.A1496@tweety.main.gnac.com> References: <3C7BF3BE.7090400@panasas.com> <20020226133410.J1141@underdog.stansell.org> <20020226225647.B77CAB5@proven.weird.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20020226225647.B77CAB5@proven.weird.com>; from woods@weird.com on Tue, Feb 26, 2002 at 05:56:47PM -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: List-Post: List-Subscribe: , List-Id: Conserver Users List-Unsubscribe: , List-Archive: There may be one way to solve at least one of these problems... http://www.datacomideas.com/Catwalk.html ASP Technologies makes a clever box (at the URL above) which was intended to let you put a local VT Terminal near the gear, and plug that into the box (CatWalk)...you then also plug in a cable from your console server as well, and a third lead that goes to the device that you care about.... Normally, the console server gets access...but someone can go to the 'local' VT terminal, and use that, by pressing a button on the box. This toggles the write access to the local port, while the console server is effectively in read-only mode. However, the console server can also pull control back, using (if I recall correctly) a handshaking line to reset the box. So, change the model a bit...use two ports from the console server, and plug the 'common' to the UPS, or whatever you really care about...Allow the conserver host to connect to one port of the console console server...and then use a reverse-TCP session to the second console server port be used for debugging (using the hardware control to steal control if it is needed)...or put both ports on conserver, and use the client to take the port (force-attach if needed), and when you relinquish it, 'regular' users can have their access to it again? Just a thought... { ASP Technologies sells a commercial console server called Vantage, and the http://www.asptech.com/ website is really only built to sell Vantage...however, the Data Com Ideas website (above) is managed by one of ASP's technical leaders, and covers a lot of the hardware hacks they have developed to make Vantage more useful. The team at ASP have their hats screwed on right, and I like the hardware hacks they've put together. -Z- } -Z-