SEO

I have a client on 5.0.7 that was asking me about ways to connect to
another terminal remotely and see what was on their screen for error
diagnosing a trouble shooting. I told them I seem to recall a product
called Double View or Double Vision. Anyone remember this and am I
correct in what it does. Also any other suggestions?


--
Brian Keener
bkeenerReMoVeAnTiSpAm@thesoftwaresource.com

Brian Keener wrote:
> I have a client on 5.0.7 that was asking me about ways to connect to
> another terminal remotely and see what was on their screen for error
> diagnosing a trouble shooting. I told them I seem to recall a product
> called Double View or Double Vision. Anyone remember this and am I
> correct in what it does. Also any other suggestions?
>
>

It's DoubleVision from tridia.com. Very good, unlimited users license is
standard.

Kernel resident, does not change how pty's are assigned. Has a good Menu
system and can translate one terminal type to another. Limited platform
availability (no Linux except for Red Hat for example).

The other commercial product I use is Peek, from computron.com, at my
Unixware sites (Unixware is only recently available for DV).

Can be cheaper for smaller sites as it has a per user license, but it
requires launching a Peek shell on login, that then launches sh/ksh/bash
whatever.

You have to script your own menu (not hard) or use the character command
line.

--
----------------------------------------------------
Pat Welch, UBB Computer Services, a WCS Affiliate
SCO Authorized Partner
Microlite BackupEdge Certified Reseller
Unix/Linux/Windows/Hardware Sales/Support
(209) 745-1401 Cell: (209) 251-9120
E-mail: patubb@inreach.com
----------------------------------------------------

Brian Keener wrote:
> I have a client on 5.0.7 that was asking me about ways to connect to
> another terminal remotely and see what was on their screen for error
> diagnosing a trouble shooting. I told them I seem to recall a product
> called Double View or Double Vision. Anyone remember this and am I
> correct in what it does. Also any other suggestions?
>
>

Has anyone installed and used VNC for this in SCO OpenServer? Or installed
emacs, and used "emacs -e shell" in order to save the contents of a shell
interaction to a file?

I've used both for many years in other OS's.

On Sat, 8 Mar 2008, Nico Kadel-Garcia wrote:
> Brian Keener wrote:
> > I have a client on 5.0.7 that was asking me about ways to connect to
> > another terminal remotely and see what was on their screen for error
> > diagnosing a trouble shooting. I told them I seem to recall a product
> > called Double View or Double Vision. Anyone remember this and am I
> > correct in what it does. Also any other suggestions?
>
> Has anyone installed and used VNC for this in SCO OpenServer? Or
> installed emacs, and used "emacs -e shell" in order to save the contents
> of a shell interaction to a file?
>
> I've used both for many years in other OS's.

Yes, I use it with UnixWare 7.1.X , OpenServer 5.0.X and OpenServer 6.0.X.
It is a poor man's way of having the abilities. It takes a bit to compile
emacs on them. Xemacs is easier.

--
Boyd Gerber <gerberb@zenez.com>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047

Nico Kadel-Garcia wrote:
> > called Double View or Double Vision. Anyone remember this and am I
> > correct in what it does. Also any other suggestions?
> >
> >
>
> Has anyone installed and used VNC for this in SCO OpenServer? Or installed
> emacs, and used "emacs -e shell" in order to save the contents of a shell
> interaction to a file?

How does this work in relation to having a user/customer running an
application and you want to see what is on his screen. Since I don't use
emacs I'm not that familiar with this. Can you provide a little more of what
would be happening and how it is used.

bk

----- Original Message -----
From: "Brian Keener" <bkeenerReMoVeAnTiSpAm@thesoftwaresource.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Friday, March 14, 2008 2:49 PM
Subject: Re: Remote Control a terminal or the console.


> Nico Kadel-Garcia wrote:
>> > called Double View or Double Vision. Anyone remember this and am I
>> > correct in what it does. Also any other suggestions?
>> >
>> >
>>
>> Has anyone installed and used VNC for this in SCO OpenServer? Or installed
>> emacs, and used "emacs -e shell" in order to save the contents of a shell
>> interaction to a file?
>
> How does this work in relation to having a user/customer running an
> application and you want to see what is on his screen. Since I don't use
> emacs I'm not that familiar with this. Can you provide a little more of what
> would be happening and how it is used.
>
> bk

DoubleVision works like this:
You install doublevision on the server.
The install script installs a kernel module and links a new kernel.
You reboot the server to get onto the new kernel.

>From that point on, all ttys, regardless of what kind of login daemon created them (facetwin vtpd, telnetd, sshd, getty (serial), getty (console), etc...), are multiplexable/shareable. In the case of serial and console tty's you can even access tty's that aren't currently logged in or that don't even have a getty running on them.

What that exactly means is:

Any user can "dv ttyxx" any other tty, subject to a plethora of permissions configurable in dv config files.

user tim is logged in on ttyp4
user root is logged in on ttyp112
user root can run "dv" and select ttyp4 from an interactive application that shows all the tty's on the system and what program and user is using them where applicable. Or you can say "dv ttyp4" and jump right there skipping the interactive dv app.

At that point:
* Both root and tim can type and the keystrokes from both keyboards go to the app running on ttyp4.
* The output from the app on ttyp4 goes to both screens on ttyp4 and ttyp112.
It's like ttyp112 goes into the background and ttyp112 becomes a clone of ttyp4. There is an escape key that the user on ttyp112 can press to break out of the dv session and get his normal tty back.

Further notables:

You can create cron jobs that direct output to console tty's that don't have getty's running on them, and then you can dv to that tty from anywhere. Example, have your tape backup direct it's output and input to/from tty12,
30 21 * * * backup.cron </dev/tty12 >/dev/tty12 2>&1
and then at some later time you can facetwin/ssh/telnet to the server and then dv tyy12 and see the output from the backup program and type into it, like to respond to some prompt or error message like "Tape full: Please insert volume 2 and press [Enter]: _"
Don't use any tty that has a getty or any other program running on it for this. tty7 through tty12 are perfect, and the redirecting stdin trick doesn't work with _all_ programs.
You can also type Alt-F12 at the console to flip to that same tty, which you always could have done regardless of dv. dv just means you can get at the same tty from anywhere.

Several people can dv in to the same tty so it can be pretty good for classes or training multiple users.

There are controls to do things like allow a particular tty or user to view-only (no typing) a particular other tty or user, and disallow say a normal user from dv-ing any tty that root is using, etc... groups and overlapping classes of users can be set up that have various permissions.

In a perfect world, dv can translate terminal control sequences from one kind of terminal to another. That is, say user1 is on ttyp1 using a wyse50 terminal (TERM=wy50). Say user2 is on ttyp2 using a scoansi terminal emulator (TERM=ansi). Without translation, multiplexing those two sessions together would just make a big mess. If ttyp2 dv'd to ttyp1, then when the app on ttyp1 outputted some data to draw stuff on the screen, the scoansi terminal on ttyp2 would receive wyse50 escape sequences, which wouldn't work. Conversely, when user2 typed any keys besides the plainest numbers & letters (arrows, pgup,pgdn,F1-F12,backspace,Del,Ins etc...) the app on ttyp1 which thinks it's talking to a wyse50, would receive scoansi byte sequences that would either mean nothing to it, or worse would mean things other than what user2 intended. (like the classic backspace vs delete issue, you press backspace, and the app thinks you pressed break and immediately exits). But dv, if your terminfo and/or termcap are good and complete and accurate for your terminals, and if the dv termtype logger was run from the users .profile or from /etc/profile, then dv can translate all the terminal-specific byte sequences between all the ttys that are sharing a session. Generally though it's simpler to just have everyone using the same type of terminal, ideally a good scoansi emulator, and then there is almost never any glitches.

--
Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!

On Mar 7, 6:48*pm, Brian Keener <bkee...@thesoftwaresource.com> wrote:
> I have a client on 5.0.7 that was asking me about ways to connect to
> another terminal remotely and see what was on their screen for error
> diagnosing a trouble shooting. *I told them I seem to recall a product
> called Double View or Double Vision. *Anyone remember this and am I
> correct in what it does. *Also any other suggestions?
>
> --
> Brian Keener
> bkeenerReMoVeAnTiS...@thesoftwaresource.com

You can also download and try the 'screen' program which is located on
the Skunkworks page. It has some limitations, it seems to only work
with vt100 emulation and you have to force all sessions to run one
way, so you are able to attach to them later. But it's open source
and it's free, if that turns you on.

No question, Double Vision is the cream of the crop from what I've
seen. But not free.

Mark

Note: sco has a built in program very similar to screen called mscreen.
But I don't think either one provides shared sessions.

SCO made a TLS package that had a facility called spyfs that was supposed to
allow one user to watch anothers tty. I never tried it myself. It didn't
saound from the instructions to be good enough for what I need. I have used
dv a lot on sco, and used to use ttysnoop (free) on linux, but haven't used
ttysnoop lately because we have to use FacetWin for our terminal emulator,
and ttysnoop can't work with FacetWin because FacetWin does not call an
external login program. DV would work because it works at the kernel level,
but dv is practically useless on linux because of the way they tie in to
specific kernels and won't work with any other version or build. There is
another product that works like ttysnoop but isn't free called peek. I
haven't tried that myself because, if I could use peek, then I could use
ttysnoop.

For our support needs we've basically been living without any replacement
for DV since switching off of SCO. For training and sales demos we use a web
based full desktop thing via http://www.beamyourscreen.com/US/Welcome.aspx

Not nearly as convenient or fast, but, for demos and training it is useful
to be able to show the whole desktop since several parts of the app cause
things to happen outside the terminal emulator window, like scanning and
printing and printing to pdf/email/fax etc..

If I could find a windows programmer to pay to finish my few remaining hacks
to Putty, and port my existing hacks up to the current putty, then I could
finally escape facetwin and get dv-like functionality back in the form of
ttysnoop. *sigh*...

--
Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!


----- Original Message -----
From: "mbennett" <mbennett@claritysoftwaresystems.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Saturday, March 15, 2008 4:19 PM
Subject: Re: Remote Control a terminal or the console.


On Mar 7, 6:48 pm, Brian Keener <bkee...@thesoftwaresource.com> wrote:
> I have a client on 5.0.7 that was asking me about ways to connect to
> another terminal remotely and see what was on their screen for error
> diagnosing a trouble shooting. I told them I seem to recall a product
> called Double View or Double Vision. Anyone remember this and am I
> correct in what it does. Also any other suggestions?
>
> --
> Brian Keener
> bkeenerReMoVeAnTiS...@thesoftwaresource.com

You can also download and try the 'screen' program which is located on
the Skunkworks page. It has some limitations, it seems to only work
with vt100 emulation and you have to force all sessions to run one
way, so you are able to attach to them later. But it's open source
and it's free, if that turns you on.

No question, Double Vision is the cream of the crop from what I've
seen. But not free.

Mark

In article <01b701c88783$cade2200$861fa8c0@tv>,
Brian K. White <brian@aljex.com> wrote:
>SCO made a TLS package that had a facility called spyfs that was supposed to
>allow one user to watch anothers tty. I never tried it myself. It didn't
>saound from the instructions to be good enough for what I need.

spyfs is handy for times when you really need to see the text flowing to a tty,
with users/apps seeing exactly the same tty name that they normally do, with
the certainty that tty behavior will be unchanged, and without the cost of
redirection through a pty. But it doesn't inject anything - it's strictly for
observing tty output.

John
--
John DuBois spcecdt@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/

Brian K. White wrote:
> Note: sco has a built in program very similar to screen called mscreen.
> But I don't think either one provides shared sessions.
>
> SCO made a TLS package that had a facility called spyfs that was supposed to
> allow one user to watch anothers tty. I never tried it myself. It didn't
> saound from the instructions to be good enough for what I need. I have used
> dv a lot on sco, and used to use ttysnoop (free) on linux, but haven't used
> ttysnoop lately because we have to use FacetWin for our terminal emulator,
> and ttysnoop can't work with FacetWin because FacetWin does not call an
> external login program. DV would work because it works at the kernel level,
> but dv is practically useless on linux because of the way they tie in to
> specific kernels and won't work with any other version or build. There is
> another product that works like ttysnoop but isn't free called peek. I
> haven't tried that myself because, if I could use peek, then I could use
> ttysnoop.
>
> For our support needs we've basically been living without any replacement
> for DV since switching off of SCO. For training and sales demos we use a web
> based full desktop thing via http://www.beamyourscreen.com/US/Welcome.aspx
>
> Not nearly as convenient or fast, but, for demos and training it is useful
> to be able to show the whole desktop since several parts of the app cause
> things to happen outside the terminal emulator window, like scanning and
> printing and printing to pdf/email/fax etc..
>
> If I could find a windows programmer to pay to finish my few remaining hacks
> to Putty, and port my existing hacks up to the current putty, then I could
> finally escape facetwin and get dv-like functionality back in the form of
> ttysnoop. *sigh*...
>

Hop over to comp.security.ssh: a number of the Putty programmers work there,
and I've been active on that group for years. Good people.

I take it you don't like VNC for this?