tburba on Mon, 6 Dec 1999 15:54:59 -0500 (EST) |
I attempted to (over)simplify the scope of the project -- for the sake of discussion. [...takes a deep breath] Our hosts have: -- discreet serial ports (/dev/ttyS#) (I know they are not part of /dev/pts/# and the Unix 98 standard) -- many telnet pseudo ports using the /dev/pts Unix 98 standard -- A very expensive, vertical market application running that requires the following, among others: -- mgetty (contractual [read expensive] obligations require it) (although, you've implied, mgetty is not an issue) -- RH6.0 (contractual [read expensive] obligations prevent us from using debian as our Distro) -- 700 sites, each having a mini-network of these machines. Each network, having both serial and pseudotty telnet connections is connected to our Home Campus via dialup modem based connections using uucp I think I'm starting to ramble on... this is just the tip of the iceberg! darxus@op.net on 12/06/99 03:15:24 PM Please respond to plug@lists.nothinbut.net To: plug@lists.nothinbut.net cc: (bcc: Thomas A Burba/USVISION) Subject: Re: [Plug] ttysnoop and /dev/vcs# On Mon, 6 Dec 1999 tburba@GLCORPIS01.usvision.com wrote: > >>>Well, how/why would you have to get it to work w/ mgetty ?<<< > mgetty has the support that we need for our dialup modem based WAN. Okay, I'm having difficulty grasping what you're trying to do. You should be able to use mgetty for your wan connections, and ttysnoops for your dumb terminal connections... ? Wait... Ah, here ya go... in the example /etc/snooptab that comes in the debian package... # example /etc/inittab (using agetty): # s2:23:respawn:/sbin/getty 38400 ttyS2 vt100 -l /usr/sbin/ttysnoops Paste me the lines in your /etc/inittab that spawn your mgetty's. It looks like you just need to add "-l /usr/bin/ttysnoops" to use ttysnoops as the login program for mgetty. I don't have the mgetty man pages handy, so I can't verify the syntax is identical to that of getty, but I'd expect it to be. >From my getty manpage: -l login_program Invoke the specified login_program instead of /bin/login. This allows the use of a non-standard login program (for example, one that asks for a dial-up password or that uses a different password file). ..and you wanna use ttysnoops as the login_program. > >>>ttysnoop is GPLed, download the code & make it work w/ unix98 PTYs :)<<< > alas, I'm not a codeslinger -- just a lowly, overworked, system engineer. > Any Volunteers? Everybody has to start somewhere :) > >>>Also, why do you need to snoop /dev/ttyS1 instead of using the a virtual > console ?<<< > each of our 700 sites around US and Canada has a console and multiple > serial dumb terminals running over dev/ttyS#. Can an actual port be > represented as a virtual console? If so, then our problem may be solved! No, that's not what I'm saying. But it sounds like you're not dealing w/ Unix98 PTYs. Unix98 PTYs look like /dev/pts/1 -- /dev/ttyS# is *not* a Unix98 PTY, and if you are using it, Unix98 PTYs are *not* the problem. I think. __________________________________________________________________ PGP fingerprint = 03 5B 9B A0 16 33 91 2F A5 77 BC EE 43 71 98 D4 darxus@op.net / http://www.op.net/~darxus Find the next largest prime, be famous: http://www.mersenne.org/prime.htm _______________________________________________ Plug maillist - Plug@lists.nothinbut.net http://lists.nothinbut.net/mail/listinfo/plug _______________________________________________ Plug maillist - Plug@lists.nothinbut.net http://lists.nothinbut.net/mail/listinfo/plug
|
|