Tao, Miao wrote: > Hi Ava, > > This looks a good solution. I just have two questions about this: > > 1. To login with same id, will this invoke conflicts on each user's > profile? Lots of applications has their own profiles when the > application is running, and will read/write data to its profile, this > might be a problem. > Some applications can control conflict by themselves. For example, user1 login via 'work' and starts up firefox, then user2 do the same thing, firefox will tell user2 that firefox is running and doesn't allow user2 to launch it. > 2. Could community users have the privilege adding a new account on test > machines? If they could, this can resolve the problem in #1. > ASAIK , only root can add user. Any idea to solve this problem?
Thanks --Ava > -Tim > On Wed, 2008-09-03 at 11:46 +0800, Ava Zhang wrote: > >> Paul, >> >> If the testing machine can be accessed out of SWAN, multi-testers can >> use Xvnc to login the machine at the same time and test most of GUI >> programs. >> This is the way we are using in our lab for multi-users login and testing. >> >> It is very easy to setup Xvnc: >> >> # Warning: restart will kill all current dtlogin sessions! >> svccfg -s cde-login setprop 'dtlogin/args=""' >> svcadm restart cde-login >> # Add xvnc service to /etc/services if it isn't already (CR 6614889) >> printf "vnc-server\t5900/tcp\t\t\t# VNC Server\n" >> /etc/services >> # Enable Xvnc inetd service: >> inetadm -e xvnc-inetd >> >> Connect from another machine with: >> vncviewer hostname:0 >> >> >> >> Thanks >> --Ava >> >> Paul wrote: >> >>> Hi All, >>> >>> We are working for the infrastructure setup for desktop testing. Now I'd >>> like to collect the feedback about remote testing requirement for >>> desktop testing. You know, the testing community in OpenSolaris >>> community has provided some hardwares and one program called "Test >>> Farm", then it can let community user leverage Sun's hardware for >>> Solaris kernel/driver development and testing. For desktop testing, >>> because all of our applications are GUI, the requirement is a little >>> different from that. So I'd like to get your feedback if we need to do >>> something like this way. If I can get enough positive feedback about it, >>> I can discuss with team about how to setup it. >>> >>> The questions can be like this: >>> 1. Do you think it is necessary to provide community user hardwares for >>> desktop application remote testing? >>> 2. If yes, could you please list some reasons? >>> >>> I'd like to set time limit from Aug. 26 to Sep. 1. Please give me your >>> feedback. >>> >>> Thanks, >>> Paul. >>> _______________________________________________ >>> desktop-testing mailing list >>> desktop-testing at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/desktop-testing >>> >>> >> _______________________________________________ >> desktop-testing mailing list >> desktop-testing at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/desktop-testing >> > > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20080903/b750559a/attachment.html>
