lestrrat has asked for the wisdom of the Perl Monks concerning the following question:

First, let me apologize for this question -- I really should do more searches before asking, but I wasn't sure on what to call this tool that I wanted. So I didn't know exactly how to search

Anyway, here's my situation:

We can log into our propietary machines via a console port. I use the output of this port in my perl tool to monitor activities, especially core dumps.

The console port only allows one telnet session to be attatched to it, but I also have to let other users access the console so that they can issue commands to the machine when the console is the only means to access the machine.

So basically I need a software which allows multiple users to connect to the same console port and share the output from the console, so that I can keep monitoring it while others do whatever they want with the console.

I just feel like this is something that others might have gone though, and that there should be a software for it. Do you guys know of anything like this out there? At least, if you kow what this is generally called, please let me know, and I'll search for it

Thanks in advance

Replies are listed 'Best First'.
Re: Share a console?
by blakem (Monsignor) on Aug 25, 2001 at 02:04 UTC
    Screen will multiplex a single login session. I used to use it all the time to emulate numerous terminals in a single display. I don't think it shares information between the screens though, so it might not be exactly what you need....

    -Blake

[reply]
Re: Share a console?
by traveler (Parson) on Aug 25, 2001 at 01:57 UTC
    This may not meet your needs, but there is a tool that allows sharing windows (X- or MS) called VNC. One scenario would be to have your tool run in a window (again, X- or MS) and share just that window using VNC (it can be password protected). All users' input is sent to the window and all output would go to all users. You can configure it to only share output with just one user doing the mouse/kbd input. For sharing just one window, be sure to get the VNC server configured that way -- the standard one shares the whole desktop!

    HTH, --traveler

[reply]
Re: Share a console?
by lestrrat (Deacon) on Aug 25, 2001 at 18:06 UTC

    Thanks guys, but not exactly what I wanted. :-(

    I'm not doing GUI, so VNC is out of the question, although that's almost the behavior I want, except, in a terminal

    Screen came up in my first tentative searches, but the description didn't quite match what I was thinking. Although, since I didn't really dig into the docs, I could be wrong

    If anybody else has more ideas, please let me know.... meanwhile I'm going to go search some more...

[reply]
      You don't need a GUI for VNC, exactly. If your computer has some windowing system on it, say X, use a terminal window on that system and share it. You can share a shell window running a terminal emulator or you can share a window on a terminal emulator such as Seyon. Are you saying your system is not running any windows at all?

      HTH, --traveler

[reply]

        Hmm, I'm confused. The VNC I know is that thing that somewhat acts like PCAnywhere. I was under the impression that it was for Windows only. If that's not what you're talking about, then I may just assuming the wrong things

        In anycase, I believe that when using VNC, you need to install the VNC server on the machine that you want to share. Unfortunately, the machine which I'd like to share the console is not a pc ( in the broader sense of the term ). Think of sharing the console to a Cisco box... I'm not dealing with a router, but it's pretty darn close.

        Please let me know if I'm wrong about the assumption I made about VNC...

[reply]
Re: Share a console?
by data64 (Chaplain) on Aug 26, 2001 at 19:10 UTC
    I am little confused on the need to share with others. In order to clarify, I am listing two scenarios below. Please tell us which (if either) is the correct one.
    • The console port just keeps displaying the information and everyone just needs to view the information.
      In that case, just capture the output and display it on some webpage somewhere.
    • Some of the users will need to type in some commands to either query the information or do other maintenance type stuff.
      In that case, your script needs to connect, retrieve the info and then disconnect. That way, anyone who needs to can still get in. Your script will handle the case that the telnet session may not be available for a while.
[reply]

Back to Seekers of Perl Wisdom