Re: [U2] Screen manager "screen" [AD]
Randy Styka wrote: There have been various posts about "screen" and its pros and cons. It is a handy program. But as some have pointed out, support can be an issue as well as various terminal emulations. I want to suggest our PEEK software. It's available for a wide variety of Unix systems and lets an authorized user see what someone is doing and to "poke" keystrokes on their behalf. We do translations between terminal emulations, so a wyse50 user can "peek" on a vt100 user, for instance. You can log the activities to a file, and can set up unattended logging of a session, to keep auditors of outside users happy. You can control who can "peek" at who and whether they can poke or not. And it's done at the Unix level and no kernel changes or even a reboot is needed. It can be used like "screen" to monitor a session from another one, to reconnect to it, etc. For more details, send an email to [EMAIL PROTECTED] or visit http://www.computronics.com Thanks! Randy and Computronics have been around for at least 20 years. They supported PR1ME sites for ages, and have gracefully transitioned to other markets. In all of the years that I've known of them, I've never heard anyone speak poorly of them, and my personal transactions with them have always been more than satisfactory. -- Allen Egerton [EMAIL PROTECTED] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Screen manager "screen" [AD]
There have been various posts about "screen" and its pros and cons. It is a handy program. But as some have pointed out, support can be an issue as well as various terminal emulations. I want to suggest our PEEK software. It's available for a wide variety of Unix systems and lets an authorized user see what someone is doing and to "poke" keystrokes on their behalf. We do translations between terminal emulations, so a wyse50 user can "peek" on a vt100 user, for instance. You can log the activities to a file, and can set up unattended logging of a session, to keep auditors of outside users happy. You can control who can "peek" at who and whether they can poke or not. And it's done at the Unix level and no kernel changes or even a reboot is needed. It can be used like "screen" to monitor a session from another one, to reconnect to it, etc. For more details, send an email to [EMAIL PROTECTED] or visit http://www.computronics.com Thanks! ++ | Computronics Randy Styka, [EMAIL PROTECTED] | | 4N165 Wood Dale Road Phone: 630/941-7767 | | Addison, Illinois 60101 USA Fax: 630/941-7714 | ++ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Screen manager "screen"
If you want to use GNU screen with emulation other than VT family
(including xterm), you have to add many tweaks in the screenrc file for
your emulation.
You might need to hack the screen to use a slave printer. If you want
to use the screen with aux. input devices, like credit card swipe reader
and pen scanner, it does not let you use them unless you configure those
devices with escape sequence the screen likes.
GNU screen also give you TANDEM like capability too (sudo + screen).
If you are just looking for a capability to attach/detach a screen
session, you might be interested in application called "dtach." Dtach
is a slender version of GNU screen.
We've been using GNU screen for 5+ years. All our associates (10,000+)
run udt sessions under the screen command.
If you are going to let (!geek) use GNU screen, you need to ask yourself
a question... "mmm...do we have C programmers who can read HUGE and
spaghetti C code for supporting GNU screen?" If the answer is NO, don't
use it. :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, December 20, 2006 5:03 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Screen manager "screen"
Good day,
Anybody using the screen manager ('screen' on linux/unix)?
Any gotchas we should know of?
We are on AIX 5.3; UV 10.1.4
Thanks.
Schalk van Zyl
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Screen manager 'screen'
Brad Schrag wrote: > We aren't using it yet, but are working on it. > > For us, screen will be used primarily by operators for long-running > processes, so we have to deal with the fact that the person who started a > job may not be around to check on it until it completes. We expect to > address this by setting up a shared userid. Operators will login as > themselves then 'sudo su' to the shared userid. Since screen attempts to > connect to the port that is already being used by the operators id, the > operators will run ssh under the shared id and then kick off screen. If > anyone has any other ideas on how to address port contention, I'd be > interested. > > This approach allows anyone with 'sudo su' to the shared id to monitor the > jobs. Using sudo helps address security concerns inherent in shared ids. > > Brad Schrag > InfoLease Development > 651-205-3074 > RiverBank / EP-MN-BGF Brad, We had the same idea, plus: Being in S Africa, we are constantly tormented with temporary breaks in communication. It looks like when using 'screen', the user will be able to re-login and simply resume with whatever he/she/it was busy doing (maybe with a cluttered display), but at least the user would be able to help herself to either complete or trash the incompleted transaction. Schalk. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Screen manager "screen"
We aren't using it yet, but are working on it.
For us, screen will be used primarily by operators for long-running
processes, so we have to deal with the fact that the person who started a
job may not be around to check on it until it completes. We expect to
address this by setting up a shared userid. Operators will login as
themselves then 'sudo su' to the shared userid. Since screen attempts to
connect to the port that is already being used by the operators id, the
operators will run ssh under the shared id and then kick off screen. If
anyone has any other ideas on how to address port contention, I'd be
interested.
This approach allows anyone with 'sudo su' to the shared id to monitor the
jobs. Using sudo helps address security concerns inherent in shared ids.
Brad Schrag
InfoLease Development
651-205-3074
RiverBank / EP-MN-BGF
The answer to life, the universe and everything
[EMAIL PROTECTED] wrote on 12/20/2006 04:03:17 AM:
> Good day,
>
> Anybody using the screen manager ('screen' on linux/unix)?
> Any gotchas we should know of?
>
> We are on AIX 5.3; UV 10.1.4
>
> Thanks.
> Schalk van Zyl
> ---
> u2-users mailing list
> u2-users@listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
>
--
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications privacy
laws, and is also confidential and proprietary in nature. If you are not the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you have
received this communication in error, and then immediately delete it. Thank you
in advance for your cooperation.
==
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
