That's an interesting question. In VHA, things have never been done this way. The MUMPS subsystem (whatever the flavor) has always run under the control of a single (pseudo-)user and then users would sign in using VA Kernel. In fact, it's not unusual to set up an account with no password but with VistA (Kernel) as its "shell". But remember that VistA originated (then called DHCP) at a time when it was not the norm for users to have their own accounts at the OS level. My VA career doesn't go back to the PDP-11 days, but it wasn't that long ago that VistA/DHCP was run on top of DOS. If VistA development were started today, I don't think it's likely that the same architecture would be used -- Or would it? Lately, I've been thinking about ways to optimize access by multiple users to the same tables/file (depending on the underlying DBMS) and it is in many ways attractive to have a single "user" accessing the database with a front-end of some sort handling synchronization and resource sharing. But then, of course, that's just what an application server is for! (Yet another way that VistA has anticipated current technology.)
--- "Bhaskar, KS" <[EMAIL PROTECTED]> wrote: > In general, this is not recommended, but should (notice I say should > not would) not be harmful as long as their terminal emulators drops > the connection when they close the terminal window. > > But why do you not give each user his/her own Linux userid? Linux > security is better than VistA security, and sharing userids and > passwords is frowned upon by the security folks. > > Also, why are folks exiting VistA? Why not stay in till it's time to > go home? > > -- Bhaskar > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of Kevin > Toppenberg > Sent: Sat 4/2/2005 5:34 PM > To: Hardhats Sourceforge > Cc: > Subject: [Hardhats-members] Need advice re Linux/GT.M login script > In my environment, the nurses will be using the > terminal access to vista only rarely (1-5 times/day). > So I am trying to figure a way that they will stay > connected to the system, and not be booted out all the > time. > > Currently there are 2 logins required. > 1st) a login & pwd to connect to the linux server via > ssh (a common set of codes for all employees) > 2nd) the vista access code/verify codes > (employee-specific) > > I would like to have the terminal stay connected, even > if they are logged out of vista. That way they will > only have to enter their vista codes in again the next > time. > > Here is the current script that is executed when users > connect to a "vista" account > > # .bashrc > # User specific aliases and functions > # Source global definitions > if [ -f /etc/bashrc ]; then > . /etc/bashrc > fi > sh runvista ^ZU > exit > #---------------------------- > > I would like to change this to a loop, like this: > > > # .bashrc > # User specific aliases and functions > # Source global definitions > if [ -f /etc/bashrc ]; then > . /etc/bashrc > fi > while [1 -eq 1] > do > sh runvista ^ZU > done > > exit > #---------------------------- > > My concern is that there is no "proper" way to exit > vista or GT.M with this method. As soon as they log > out, they will be prompted to log back in. Thus they > would just exit the terminal application to shut down > the computer at night. > > Would this be harmful for vista or GT.M (i.e. the > equivelent of a crash?) > > Thanks > Kevin > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Personals - Better first dates. More second dates. > http://personals.yahoo.com > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Hardhats-members mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/hardhats-members > > > > A practical man is a man who practices the errors of his forefathers. --Benjamin Disraeli ==== Greg Woodhouse [EMAIL PROTECTED] [EMAIL PROTECTED] ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
