Sounds very similar to what I want to achieve; however, our "accounts" within our software are not Windows/UV accounts (these are master by customer); but rather are stored inside a file once the first phase of authentication passes (Username and account name or path puts our customers in the correct customer environment. Once logged in there; which is automated with a script; the user then logs in with their own username and password which lives within the UV environment; it has no parallel in Windows.)
I suppose I'll have to get creative and see if there are any provisions in the screen manual. Or perhaps write a process to update /etc/passwd from our EMPLOYEES file to match. I am certain I can make this work with some practice -- how did you implement this? Thanks - Gabe On Jan 22, 2008 9:20 PM, phil walker <[EMAIL PROTECTED]> wrote: > We use screen for RF sessions which drop out leaving sessions around. It > works quite will, we restrict the user to one UV session and do some > checking around connections to ensure that the user and only the user > can connect to a screen session if one is there otherwise it is a usual > connect. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Gabriel Green > Sent: Wednesday, 23 January 2008 5:01 p.m. > To: [email protected] > Subject: [U2] Problems with disconnects - telnet > > Hi all, > > Back in the mvBASE days, a telnet disconnect would allow an interactive > user's activities to continue. UV is "smarter" than this, however, and > is > quick to get rid of disconnected users. At least, it does not behave in > the > same way. > > What I would like to know is if there are facilities within UV to allow > this > sort of behavior. > > One scenario I dreamed up involved using the UNIX utility screen (which > has > been ported to Windows with cygwin). The issue would be tying screen > sessions to existing telnet sessions and incorporating security so that > we > do not have people resuming one another's screen sessions. Has anyone > attempted this? Or is there a third party tool to do this? > > The key thing is: as much transparency to the end user as possible. The > tools we have available on the client side are AccuTerm 2K2; and UV > (running > on various flavors of Windows 2000-2003) on our servers. If screen is a > potential solution, the cygwin layer could be installed. > > The reason I ask is because disconnects - which we have some control > over; > but often is left to the whims of customer infrastructure, can cause > garbed > up transactions; which gives us untold headaches. > > Ideas, anyone? We wouldn't go back to mvBASE if our lives depended on > it; > but we do need to solve the disconnect issues for our customers who > refuse > to pay for high quality data connections to our servers and the > associated > equipment. > > Thanks much, > Gabe > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
