From toby.gerhart@eds.com Fri Aug 1 13:32:18 2003 Received: from plmler5.mail.eds.com (plmler5.mail.eds.com [199.228.142.70]) by underdog.stansell.org (8.12.9/8.12.9) with ESMTP id h71KWI3A006269 for ; Fri, 1 Aug 2003 13:32:18 -0700 (PDT) Received: from plmlir5.mail.eds.com (plmlir5-2.mail.eds.com [199.228.142.135]) by plmler5.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h71KWHH10800 for ; Fri, 1 Aug 2003 15:32:17 -0500 Received: from plmlir5.mail.eds.com (localhost [127.0.0.1]) by plmlir5.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h71KWF401468 for ; Fri, 1 Aug 2003 15:32:16 -0500 (CDT) Received: from usplm102.exsc01.exch.eds.com (USPLM102.txpln.us.eds.com [198.132.135.15]) by plmlir5.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h71KWFh01460 for ; Fri, 1 Aug 2003 15:32:15 -0500 (CDT) Received: by USPLM102.txpln.us.eds.com with Internet Mail Service (5.5.2656.59) id ; Fri, 1 Aug 2003 15:32:14 -0500 Message-ID: From: "Gerhart, Toby C" To: users@conserver.com Date: Fri, 1 Aug 2003 15:32:12 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain Subject: Question - HP Superdome X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 20:32:19 -0000 > We have CISCO equipment supporting a number of different environments > including HP, SUN, PIX firewalls, etc. > > I have a problem when attaching to a HP Superdome....I can initially > manipulate on the GSP fine until actually selecting the menu item to go to > a specific domain's server console. Immediately at that point, it seems > to immediately go into spy mode even when I do the force attach/read-write > as it requests. Is there something that I am doing wrong or is there a > work around? > > Thanks for any help. > > From William.Bianco@sungard.com Sat Aug 2 12:02:09 2003 Received: from corp-mail02.sungard.com (corp-mail02.sungard.com [216.83.180.44]) by underdog.stansell.org (8.12.9/8.12.9) with ESMTP id h72J283A012179 for ; Sat, 2 Aug 2003 12:02:08 -0700 (PDT) Received: from Corp-SMTP2 (unverified) by corp-mail02.sungard.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Sat, 2 Aug 2003 15:02:07 -0400 From: William.Bianco@sungard.com To: users@conserver.com Message-ID: Date: Sat, 2 Aug 2003 15:02:04 -0400 X-MIMETrack: Serialize by Router on Corp-SMTP2/SunGard(Release 5.0.10 |March 22, 2002) at 08/02/2003 02:01:00 PM MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" Subject: William Bianco/Philadelphia/Recovery is out of the office. X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2003 19:02:10 -0000 I will be out of the office starting 07/25/2003 and will not return until 08/04/2003. If you require any immediate action please contact Bob Kurz. at 215-351-3208. From jh@axis.com Sun Aug 3 21:19:32 2003 Received: from miranda.se.axis.com ([212.209.10.215]) by underdog.stansell.org (8.12.9/8.12.9) with ESMTP id h744JV3A021062 for ; Sun, 3 Aug 2003 21:19:31 -0700 (PDT) Received: from aivas.se.axis.com (jh-vtun-laptop.se.axis.com [10.2.8.6]) by miranda.se.axis.com (8.12.8p1/8.12.8/Debian-2woody1) with ESMTP id h744JMrG018121 for ; Mon, 4 Aug 2003 06:19:22 +0200 Received: from aivas.se.axis.com (localhost [127.0.0.1]) by aivas.se.axis.com (8.12.9/8.12.9/Debian-3) with ESMTP id h744JJPP016246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 4 Aug 2003 06:19:19 +0200 Received: from axis.com (jh@localhost) by aivas.se.axis.com (8.12.9/8.12.9/Debian-3) with ESMTP id h744JJPV016236 for ; Mon, 4 Aug 2003 06:19:19 +0200 X-Authentication-Warning: aivas.se.axis.com: jh owned process doing -bs To: users@conserver.com From: =?iso-8859-1?Q?J=F6rgen_H=E4gg?= MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" X-Mailer: jevim v3.11 Date: Mon, 04 Aug 2003 06:19:19 +0200 Message-ID: <16235.1059970759@axis.com> Sender: jorgen.hagg@axis.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by underdog.stansell.org id h744JV3A021062 Subject: 64-bit systems? X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 04:19:33 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Could someone explain the problem with 64bit & conserver? What would happen if I add --with-64bit to the conserver package? Would it still work for 32bit systems? - -------------------------- (This is cut from a bug report from Dann Frazier compiling the Debian package of conserver on a ia64 architecture.) . . . checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for long... yes checking size of long... 8 configure: error: cannot build on >32bit systems (to override use --with-64bit) make: *** [configure-stamp] Error 1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Ld7GygfmFBKqHbgRAjzaAJsHHAI4X9bfFq8sCys4WTHHbkf2qgCfYrsU boaNbGUYG7+5+fjjdMU9dWE= =1xCf -----END PGP SIGNATURE----- From bryan@stansell.org Mon Aug 4 05:01:04 2003 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.9/8.12.9) with ESMTP id h74C143A025660 for ; Mon, 4 Aug 2003 05:01:04 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.9/8.12.9/Submit) id h74C14Hp025659 for users@conserver.com; Mon, 4 Aug 2003 05:01:04 -0700 (PDT) Date: Mon, 4 Aug 2003 05:01:04 -0700 From: Bryan Stansell To: users@conserver.com Message-ID: <20030804120104.GB25558@underdog.stansell.org> References: <16235.1059970759@axis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16235.1059970759@axis.com> User-Agent: Mutt/1.4.1i Subject: Re: 64-bit systems? X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 12:01:05 -0000 On Mon, Aug 04, 2003 at 06:19:19AM +0200, Jorgen Hagg wrote: > Could someone explain the problem with 64bit & conserver? basically, it's untested. > What would happen if I add --with-64bit to the conserver package? > Would it still work for 32bit systems? if you add --with-64bit, it should "just work". the --with-64bit flag doesn't do anything on a 32bit system. i believe there is at least one person out there successfully running conserver on a 64bit system, but i can't guarantee it. there were issues in the past with passing 64bit values to library calls that expected 32bit values. sometimes compilations would fail, other times it compiled but got run-time errors. the library calls i'm talking about are various ipv4 calls (can't remember which, exactly). so, in theory all the right data types are being used and a 64bit system will "just work". but, there's the chance it won't since it hasn't been tested, and maybe it's only certain 64bit systems that will work. i'd love to know for sure if 64bit compilation works...and if so, we can just remove the need for --with-64bit it's just a configure check for paranoia. Bryan From Adam.Morris@providence.org Mon Aug 4 08:55:14 2003 Received: from phsornt424.or.providence.org (phsor-nat2.providence.org [170.220.2.14]) by underdog.stansell.org (8.12.9/8.12.9) with ESMTP id h74FtE3A026076 for ; Mon, 4 Aug 2003 08:55:14 -0700 (PDT) Received: from PickupDirectory by phsornt424.or.providence.org with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PP9H5N3M; Mon, 4 Aug 2003 08:55:23 -0700 Received: from phsorcon06.or.providence.org ([170.220.78.187]) by phsornt424.or.providence.org with Microsoft SMTPSVC(5.0.2195.2966); Mon, 4 Aug 2003 08:55:23 -0700 Received: from phsormsg06.or.providence.org ([170.220.73.87]) by phsorcon06.or.providence.org with Microsoft SMTPSVC(5.0.2195.5329); Mon, 4 Aug 2003 08:55:13 -0700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 content-class: urn:content-classes:message MIME-Version: 1.0 Importance: normal Priority: normal Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 4 Aug 2003 08:55:12 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: 64-bit systems? Thread-Index: AcNagB08N2nxKpo/SxKXgCUlksCh6QAIBf3g From: To: X-OriginalArrivalTime: 04 Aug 2003 15:55:13.0420 (UTC) FILETIME=[CA715CC0:01C35AA0] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by underdog.stansell.org id h74FtE3A026076 Subject: RE: 64-bit systems? X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2003 15:55:15 -0000 Greetings, I'm running conserver in 64 bit on hp-ux. I can't remember the differences off hand, but it was a difference in types between a 32-bit and 64-bit system... I haven't upgraded yet as someone took my console server away "for a few weeks" and I still don't have it back... :-( You should just try it with the --with-64bit flag and see if it works. If it does then please let everyone know and perhaps Bryan can eventually remove the "warning" message. Adam DISCLAIMER: This message is intended for the sole use of the individual 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 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 this message. From bryan@stansell.org Fri Aug 8 08:27:58 2003 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.9/8.12.9) with ESMTP id h78FRw3A012711; Fri, 8 Aug 2003 08:27:58 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.9/8.12.9/Submit) id h78FRwWf012710; Fri, 8 Aug 2003 08:27:58 -0700 (PDT) Date: Fri, 8 Aug 2003 08:27:58 -0700 From: Bryan Stansell To: announce@conserver.com, users@conserver.com Message-ID: <20030808152758.GB12306@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Cc: Subject: conserver-8.0.0-beta3 is available X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2003 15:27:59 -0000 I just made the latest beta available at http://www.conserver.com/beta/. The main I/O loops have been radically changed to remove alarm() calls, buffer write() data and make all sockets non-buffered. Data sent to consoles used to be written one byte at a time - now it's sent in as big of a chunk as it's received. Any and all feedback is appreciated. Here is the list of changes... version 8.0.0-beta3 (Aug 8, 2003): - master process no longer forks on client requests - handles them with select() like child process - alarm()/SIGALRM usage removed and replaced with counters and timer on select() call - removed caching of timeouts to terminal servers - each socket connection now has a proper timeout (and can happen simultaniously) - partial write()s are properly buffered and retried - made all sockets (including SSL) non-buffered - client now supports piping data to it and properly printing all server data ("echo '^Ecr^Ec.' | console universe") Bryan Stansell From holland@guidancetech.com Wed Aug 13 05:33:07 2003 Received: from wink.pobox.com (wink.pobox.com [207.106.49.21]) by underdog.stansell.org (8.12.9/8.12.9) with ESMTP id h7DCX33A014891 for ; Wed, 13 Aug 2003 05:33:07 -0700 (PDT) Received: from texas.pobox.com (texas.pobox.com [64.49.223.111]) by wink.pobox.com (Postfix) with ESMTP id 99792FDF6 for ; Wed, 13 Aug 2003 08:33:01 -0400 (EDT) Received: from hackintosh (unknown [144.71.77.200]) by texas.pobox.com (Postfix) with ESMTP id DCA4E45356 for ; Wed, 13 Aug 2003 08:33:00 -0400 (EDT) From: "Rich Holland" To: Date: Wed, 13 Aug 2003 08:33:00 -0400 Organization: Guidance Technologies, Inc. Message-ID: <001401c36197$08b2aff0$c8964790@hackintosh> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: Question - HP Superdome X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list Reply-To: holland@pobox.com List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2003 12:33:09 -0000 Someone posted a request a couple weeks ago about using the conserver in an HP Superdome environment; I passed the question on to a friend who does this and here's his response: > PROBLEM > > While trying to connect to the *GSP* on the IP address, *gsp* > is give the following error: > > *Force to *spy* *mode* by user admin* > > What is causing this, and how can it be corrected? > > CONFIGURATION > > HPUX-OS 11.x > Superdome 32-way > > RESOLUTION > > In this case, it was necessary to kill the shell process > (pid) in order to start a new getty. The procedure to do > this follows. > > 1) Check if there is a getty running on the console: > > hostname:/home/root/.secure/etc#ps -ef | grep console > root *18489* 1 0 Sep 16 console 0:00 -sh > root 21620 18058 0 18:29:07 pts/4 0:00 grep console > > hostname:/home/root/.secure/etc#ps -ef | grep getty > root 21642 18058 0 18:29:18 pts/4 0:00 grep getty > > ===> no getty running on console > > 2) Try to start with init q > > ==> If still no getty, go to step 3 > > 3) Kill the shell that was running on console: > > hostname:/home/root/.secure/etc#kill -9 *18489* (use the > pid of the -sh above) > > 4) Check for a getty again: > > hostname:/home/root/.secure/etc#ps -ef | grep getty > root 21687 1 0 18:29:41 console 0:00 > /usr/sbin/getty console console > root 21707 18058 0 18:29:47 pts/4 0:00 grep getty > > 5) *You should now be able to login on console via gsp.* > > *BACKGROUND:* > > If the hung shell process has filled up the audit log, you > may also have to copy these 2 files to another directory and > create new, empty files. The problem would be manifested > after using a Ctrl B and receiving this message: > > "..file system of audit has 0% left you must specify a > backup file now and attempt to switch to backup file failed". > > Use the command: ll /home/root/.secure/etc > to check the file sizes of audfile1 and audfile2, then after > copying them to a backup directory, recreate new files with > the commands: > > # cat /dev/null > /home/root/.secure/etc/audfile1 > # cat /dev/null > /home/root/.secure/etc/audfile2 Hope this helps! -- Rich Holland (913) 645-1950 SAP Technical Consultant print unpack("u","92G5S\=\"!A;F]T:&5R(\'!E; Tue, 19 Aug 2003 07:34:43 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.9/8.12.9/Submit) id h7JEYhwW028376 for users@conserver.com; Tue, 19 Aug 2003 07:34:43 -0700 (PDT) Date: Tue, 19 Aug 2003 07:34:43 -0700 From: Bryan Stansell To: users@conserver.com Message-ID: <20030819143442.GB28195@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: i could use some feedback on break sequences X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2003 14:34:44 -0000 i've finally added delays to break sequences in hopes that sun alt-break and LOM interactions would work more reliably. i'd like to insert proper delays into the pre-defined break sequences, but i'm not sure if they're really necessary or where they should go. so, here are my thoughts about alt-break. i've seen references (to older 2.6/2.7 patches, i believe) that state you need a 0.5 second delay between characters in the '\r~^b' alt-break sequences (using no more than 5 seconds). i've also see references (solaris 8/9) that state you shouldn't run binary protocols over the serial port with the alt-break enabled as it could be interpreted as the break sequences. so, it leads me to believe they removed the requirement for a 0.5 second delay between characters. i'm tempted to insert the delays to be backward compatible with the 2.6/2.7 patches...but if anyone can verify that the delays aren't necessary (or definitely are), i'd love to know it. as for the LOM interaction, there is currently a '#.reset -x\r' pre-defined. should there be a delay between the '#.' and the 'reset'? from the very little i remember, there is a pause and i think a potential for data loss if the 'reset' comes too quickly. but, again, i can't verify it. i figured giving the LOM a chance to break out and produce a prompt would be a good thing. can someone with a LOM-based machine provide experiences with it? i've looked back at the mailing list archives and seen references to folks having trouble with things and needing delays. i just wanted to get the hard specifics on placement so the defaults could be improved. please send all your feedback directly to me instead of the list. if you feel you have something useful for everyone, then yes, share with the list, but stuff like "works for me" or "i vote for the delay here" should really just come to me. for those still with me, the delay is triggered with at '\d' spec in the break sequence and it causes a 0.33 second sleep. yes, that sleep puts the entire process on hold for 0.33 seconds, but the cool thing is if you do '\d\d\d' in the sequence, client and console data is checked and processed between the 0.33 second delays, so you can't really hurt the server too badly by stacking up the delays (a serial break [\z] can cause a delay too, and it is handled the same way). why 0.33 seconds? just seemed like a long enough time to be useful and short enough not to cause excessive delay. thanks much folks. 8.0.0-beta4 should be pretty cool. ;-) Bryan From bryan@stansell.org Sun Aug 24 17:33:46 2003 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.12.9/8.12.9) with ESMTP id h7P0Xk3A012028; Sun, 24 Aug 2003 17:33:46 -0700 (PDT) Received: (from bryan@localhost) by underdog.stansell.org (8.12.9/8.12.9/Submit) id h7P0Xkpq012027; Sun, 24 Aug 2003 17:33:46 -0700 (PDT) Date: Sun, 24 Aug 2003 17:33:45 -0700 From: Bryan Stansell To: announce@conserver.com, users@conserver.com Message-ID: <20030825003345.GA12008@underdog.stansell.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Cc: Subject: conserver-8.0.0-beta4 is available X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.2 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2003 00:33:47 -0000 It's hard to know where to start with this set of updates. Check the details below and the manpages for info on the new items. The big thing is that about the client/server protocol has changed - allowing all information to be encrypted via SSL (if compiled in). It also allowed for the addition of various pieces of new functionality. I'm hoping this will be the last beta before the official 8.0.0 release. I don't envision any additional pieces of functionality, just compatibility issues (if anyone makes me aware of them), manpage updates, and fixes to existing code. Here's the complete list of changes... version 8.0.0-beta4 (Aug 24, 2003): - totally rewrote the client/server communication, allowing SSL connections to occur first, protecting *all* information - added 'admin' keyword to the 'access' portion of the config file for specifying users able to issue the 'quit' command - removed client -G option since it's not really useful any more - added client -t option for sending "text messages" to users, which is similar to broadcast messages, but you can specify the user and/or console - suggested by Trevor Fiatal - added client -d option for disconnecting users specified by username and/or console - suggested by Trevor Fiatal - removed --with-64bit configure option as 64bit operation is reported to work just fine - break strings with '\d' are interpreted as a delay, which can be specified in the config file (default 250ms) - removed 'reset -x' portion of default break sequence #3 - remote conserver hostnames now properly match - had to be a character string match previously - hostname aliases now checked against access lists and the matched name is used for logging - added --with-trustrevdns to enable the use of reverse DNS information for access list checks [not recommended] - see the INSTALL file for full details on who should actually need this Many thanks to Chuck Rouzer for all the help with FreeBSD support and the following issues... - fixed 'make test' problem on hosts where 'localhost' doesn't resolve to 127.0.0.1 - fixed interface probe problem under *BSD - added openpty() interface for pty allocation Bryan Stansell