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 [email protected] To unsubscribe please visit http://listserver.u2ug.org/
