From egan@sense.net Tue Feb 1 10:39:15 2005 Received: from mars.sense.net (sense.net [204.228.135.204]) by underdog.stansell.org (8.13.2/8.13.2) with ESMTP id j11Id6Tv019046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 1 Feb 2005 10:39:13 -0800 (PST) Received: from oberon (localhost [127.0.0.1]) by mars.sense.net (8.12.11/8.12.11) with ESMTP id j11Id5NJ003616 for ; Tue, 1 Feb 2005 11:39:05 -0700 From: "Egan Ford" To: Date: Tue, 1 Feb 2005 11:39:03 -0700 Organization: Sense/Net Message-ID: <02a101c5088d$4dd569d0$0183a8c0@oberon> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by underdog.stansell.org id j11Id6Tv019046 Subject: Signals to pipe processes X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.5 Precedence: list Reply-To: egan@sense.net List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2005 18:39:16 -0000 I am still using conserver 7.2.5, I have custom scripts (e.g. |script.pl) in conserver.cf. When conserver is shutdown what signals are sent to processes created with | in conserver.cf? I am checking for HUP and TERM, but fail to catch any. Thanks. From bryan@stansell.org Tue Feb 1 14:25:25 2005 Received: from underdog.stansell.org (localhost [127.0.0.1]) by underdog.stansell.org (8.13.2/8.13.2) with ESMTP id j11MPPDH021020 for ; Tue, 1 Feb 2005 14:25:25 -0800 (PST) Received: (from bryan@localhost) by underdog.stansell.org (8.13.2/8.13.2/Submit) id j11MPPxU021019 for users@conserver.com; Tue, 1 Feb 2005 14:25:25 -0800 (PST) Date: Tue, 1 Feb 2005 14:25:25 -0800 From: Bryan Stansell To: users@conserver.com Message-ID: <20050201222525.GQ18123@underdog.stansell.org> References: <02a101c5088d$4dd569d0$0183a8c0@oberon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <02a101c5088d$4dd569d0$0183a8c0@oberon> User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.39 Subject: Re: Signals to pipe processes X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.5 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2005 22:25:26 -0000 On Tue, Feb 01, 2005 at 11:39:03AM -0700, Egan Ford wrote: > I am still using conserver 7.2.5, I have custom scripts (e.g. |script.pl) in > conserver.cf. When conserver is shutdown what signals are sent to processes > created with | in conserver.cf? > > I am checking for HUP and TERM, but fail to catch any. well, in *theory* when the server shuts down it "downs" all the consoles as it's exiting, which results in a SIGHUP (yeah, not the most appropriate signal) sent to all the programs (the original idea was that it would be a shell running which would interpret that as a "go away now"). i'm not 100% sure the code works right (as i haven't tested it), so there could be issues. using 7.2.7 might make that work better...or may not change things at all. you should be seeing the SIGHUP when you do a '^Ecd' as well...if not, something's going on. oh...just has a thought. a shell is invoked (sh -c "cmd"), so the shell would be seeing the HUP, and not the program. that's probably the issue. at least, that's my guess. Bryan From phil@metallica.usc.edu Fri Feb 18 01:34:06 2005 Received: from metallica.usc.edu (metallica.usc.edu [128.125.10.57]) by underdog.stansell.org (8.13.2/8.13.2) with ESMTP id j1I9Xw3D006211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 18 Feb 2005 01:34:04 -0800 (PST) Received: from metallica.usc.edu (localhost.localdomain [127.0.0.1]) by metallica.usc.edu (8.12.11/8.12.11) with ESMTP id j1I9bKLF029571 for ; Fri, 18 Feb 2005 01:37:20 -0800 Received: (from phil@localhost) by metallica.usc.edu (8.12.11/8.12.11/Submit) id j1I9bK2D029570 for users@conserver.com; Fri, 18 Feb 2005 01:37:20 -0800 Date: Fri, 18 Feb 2005 01:37:20 -0800 From: Phil Dibowitz To: users@conserver.com Message-ID: <20050218093720.GZ16881@usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dGBDEx8Ycw1mGAPo" Content-Disposition: inline User-Agent: Mutt/1.5.4i X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 Subject: conserver coreing X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.5 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 09:34:06 -0000 --dGBDEx8Ycw1mGAPo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Conserver started coring on us tonight out of nowhere. BT: #0 0xff0518a0 in _memset () #1 0xfec4d754 in krb5_kt_free_entry () #2 0xfecc738c in key_in_keytab () #3 0xfecc350c in _ex_text0 () #4 0xff212e1c in run_stack () #5 0xff213124 in pam_authenticate () #6 0x19dd0 in CheckPass () #7 0x1afc0 in CheckPasswd () #8 0x24c64 in DoNormalRead () #9 0x256d0 in Master () #10 0x23e8c in main () We're on .10, on Solaris. Any ideas? --=20 Phil Dibowitz Systems Architect and Administrator Enterprise Infrastructure / ISD / USC UCC 174 - 213-821-5427 --dGBDEx8Ycw1mGAPo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFCFbdQ7lkZ1Iyv898RAhQTAKCbiJ/UBL0a5K9TWiKNwDwe4WH4FQCeK0Uo Eo9eHxQtjBldwR15sZNhPYk= =e1Ij -----END PGP SIGNATURE----- --dGBDEx8Ycw1mGAPo-- From phil@metallica.usc.edu Fri Feb 18 01:44:22 2005 Received: from metallica.usc.edu (metallica.usc.edu [128.125.10.57]) by underdog.stansell.org (8.13.2/8.13.2) with ESMTP id j1I9iFZB006308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 18 Feb 2005 01:44:20 -0800 (PST) Received: from metallica.usc.edu (localhost.localdomain [127.0.0.1]) by metallica.usc.edu (8.12.11/8.12.11) with ESMTP id j1I9lbj3029596 for ; Fri, 18 Feb 2005 01:47:37 -0800 Received: (from phil@localhost) by metallica.usc.edu (8.12.11/8.12.11/Submit) id j1I9lafS029595 for users@conserver.com; Fri, 18 Feb 2005 01:47:36 -0800 Date: Fri, 18 Feb 2005 01:47:36 -0800 From: Phil Dibowitz To: users@conserver.com Message-ID: <20050218094736.GA16881@usc.edu> References: <20050218093720.GZ16881@usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dR4O/ODN76kRZ1HO" Content-Disposition: inline In-Reply-To: <20050218093720.GZ16881@usc.edu> User-Agent: Mutt/1.5.4i X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 Subject: Re: conserver coreing X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.5 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 09:44:23 -0000 --dR4O/ODN76kRZ1HO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 18, 2005 at 01:37:20AM -0800, Phil Dibowitz wrote: > Conserver started coring on us tonight out of nowhere. BT: >=20 > #0 0xff0518a0 in _memset () > #1 0xfec4d754 in krb5_kt_free_entry () > #2 0xfecc738c in key_in_keytab () > #3 0xfecc350c in _ex_text0 () > #4 0xff212e1c in run_stack () > #5 0xff213124 in pam_authenticate () > #6 0x19dd0 in CheckPass () > #7 0x1afc0 in CheckPasswd () > #8 0x24c64 in DoNormalRead () > #9 0x256d0 in Master () > #10 0x23e8c in main () And here's what an strace shows when it dies: lseek(9, 0, SEEK_CUR) =3D 62 llseek(9, 0, SEEK_CUR) =3D 62 read(9, 0xFF03FD6C, 1) =3D 0 llseek(9, 0, SEEK_CUR) =3D 62 fcntl(9, F_SETLKW, 0xFFBFEC8C) =3D 0 close(9) =3D 0 Incurred fault #5, FLTACCESS %pc =3D 0xFEC5F954 siginfo: SIGBUS BUS_ADRALN addr=3D0x6835D421 Received signal #10, SIGBUS [default] siginfo: SIGBUS BUS_ADRALN addr=3D0x6835D421 --=20 Phil Dibowitz Systems Architect and Administrator Enterprise Infrastructure / ISD / USC UCC 174 - 213-821-5427 --dR4O/ODN76kRZ1HO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFCFbm47lkZ1Iyv898RArPjAKDbwLoU1vHXCuAv5gM1rvhW1E3SiQCdHANX cWWL3po6v/InXk1BLmU3K3k= =UpDx -----END PGP SIGNATURE----- --dR4O/ODN76kRZ1HO-- From phil@metallica.usc.edu Fri Feb 18 15:16:32 2005 Received: from metallica.usc.edu (metallica.usc.edu [128.125.10.57]) by underdog.stansell.org (8.13.2/8.13.2) with ESMTP id j1INGP1F014268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 18 Feb 2005 15:16:31 -0800 (PST) Received: from metallica.usc.edu (localhost.localdomain [127.0.0.1]) by metallica.usc.edu (8.12.11/8.12.11) with ESMTP id j1INJnPL007050 for ; Fri, 18 Feb 2005 15:19:49 -0800 Received: (from phil@localhost) by metallica.usc.edu (8.12.11/8.12.11/Submit) id j1INJncG007049 for users@conserver.com; Fri, 18 Feb 2005 15:19:49 -0800 Date: Fri, 18 Feb 2005 15:19:49 -0800 From: Phil Dibowitz To: users@conserver.com Message-ID: <20050218231948.GV16881@usc.edu> References: <20050218093720.GZ16881@usc.edu> <20050218094736.GA16881@usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="g7kzd1xyC43vxRgq" Content-Disposition: inline In-Reply-To: <20050218094736.GA16881@usc.edu> User-Agent: Mutt/1.5.4i X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 Subject: Re: conserver coreing X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.5 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 23:16:33 -0000 --g7kzd1xyC43vxRgq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 18, 2005 at 01:47:36AM -0800, Phil Dibowitz wrote: > On Fri, Feb 18, 2005 at 01:37:20AM -0800, Phil Dibowitz wrote: > > Conserver started coring on us tonight out of nowhere. BT: For those of us interested... it wasn't a conserver issue.... it was an environmental library issue. All solved. --=20 Phil Dibowitz Systems Architect and Administrator Enterprise Infrastructure / ISD / USC UCC 174 - 213-821-5427 --g7kzd1xyC43vxRgq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFCFngU7lkZ1Iyv898RAtD8AJwKdqmeKfJCDevZ24++RdzyAys9LACg4eWT 1L8pbs43eEtxDt+RDU/gfzk= =KCKC -----END PGP SIGNATURE----- --g7kzd1xyC43vxRgq-- From mtdolan@twinight.org Mon Feb 28 09:29:16 2005 Received: from dawn.twinight.org (dawn.twinight.org [65.39.69.132]) by underdog.stansell.org (8.13.2/8.13.2) with ESMTP id j1SHT97J006425 for ; Mon, 28 Feb 2005 09:29:14 -0800 (PST) Received: by dawn.twinight.org (Postfix, from userid 2016) id 8E06710B64; Mon, 28 Feb 2005 12:29:05 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by dawn.twinight.org (Postfix) with SMTP id 85C5DB253 for ; Mon, 28 Feb 2005 12:29:05 -0500 (EST) Date: Mon, 28 Feb 2005 12:29:05 -0500 (EST) From: Michael Dolan To: users@conserver.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 Subject: Connect Securely to Lantronix SC1620 "ports" X-BeenThere: users@conserver.com X-Mailman-Version: 2.1.5 Precedence: list List-Id: Conserver Users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 17:29:16 -0000 We have a dozen or so Lantronix SC1620s (V 4.4.1) and we would like to make secure connections to the "serial ports" of each device. The current firmware allows for an IP connection to the SC1620 and then specify the port number and it will pass you through just fine. But we cannot do the same with SSH/ssl encrypted connections, and Lantronix claims that it isnt supported in the lower models (like ours). Has anyone out there dealt with these or devised a nice work around to this problem? Thanks, -dolan