I read back over my message and see it wasn't quite clear enough. My objective is for them to log in as *non-root*, that is, with the general user account that was set up for them. As it stands now, when I start VNC I am presented with a *VNC* password screen that upon authentication takes me to a root GUI (gnome). What I was trying to explain at first was the clones I use from more experienced admins already has VNC configured, but instead of asking for a VNC password, it merely asks for the Linux id/pw of the user, and logs them into a GUI for *their* account. For some reason, when I install VNC on my own from scratch I can't replicate that behavior. I get the scenario in the 3rd sentence above. That is not what I want.
Thanks! On Wed, Oct 1, 2014 at 9:32 AM, Veencamp, Jonathon D. <jdveenc...@fedins.com > wrote: > What we do when people want to actually sign on to VNC as root, below are > the two files that need to be modified, and then xdm and xinetd restarted. > > So I made a script to replace those files with root-enabled-logon, and > then the system self-schedules to turn that off at midnight (because you > can't trust users to lock the door behind them) > > This is useful for vendor products that insist on GUI root installs. If > you are cool with root, and not forced to solve the problem via sudo, then > this works. > > Vncallowroot.sh > #!/bin/sh > > # Allow root access to gui by replacing file > sudo cp /etc/sysconfig.bak/displaymanager.root > /etc/sysconfig/displaymanager > sudo cp /etc/opt/gnome/gdm/gdm.conf.root /etc/opt/gnome/gdm/gdm.conf > # > service xdm restart > service xinetd restart > # > # Undoes this at mightnight by Scheduling file to be replaced again at > midnight > at -f /opt/local/bin/vncdenyroot midnight > > > > and the vncdenyroot script does the opposite. > > > -----Original Message----- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Berthold Gunreben > Sent: Wednesday, October 01, 2014 8:27 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Letting all users log into Tight VNC > > On Wed, 1 Oct 2014 03:34:38 -0400 > Cameron Seay <cws...@gmail.com> wrote: > > > Hello again! > > > > I am running SuSE 11 SP3, and am using an image that was set up for > > me. It seems when I use a clone from one of the gurus VNC *always* > > allows users to log in under their own id/pw. If they are non-root, > > they, of course, have no root permissions. When I use install media > > myself I have to 1. go in and configure xstartup to use gnome by > > default (which now is no problem) and, 2) I can only use VNC as > > root. I still cannot figure the trick in number 2 out. I looked for > > the xstartup in the clones I get from more experienced folks in .vnc > > and *I don't see it*. When I do my own install of VNC xstartup > > is .vnc. Also, with the clones I don't have to use a VNC password, > > just the userid and pw of that specific user. > > > > Bottom line: I need to let my students log into VNC under their own > > account. > > ok ... let me guess: what you want to do is > > 1. run yast2 remote > > and allow remote administration > > 2. make sure that your system starts in graphical mode (runlevel 5). > > Now, to let your students in, the authentication subsystem must be > configured to know them. This is either by some local users, or by > configuring some remote authentication like LDAP or NIS > > When connecting to the system with VNC, you will be then presented a > GDM (or XDM if GDM is not installed) where all locally available users > should be able to logon. > > Berthold > > -- > ---------------------------------------------------------------------- > Berthold Gunreben Build Service Team > http://www.suse.de/ Maxfeldstr. 5 > SUSE LINUX Products GmbH D-90409 Nuernberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer > HRB 16746 (AG Nürnberg) > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > ________________________________ > > The information contained in this e-mail message is intended only for the > personal and confidential use of the designated recipient(s) named above. > This message may be an attorney-client or work product communication which > is privileged and confidential. It may also contain protected health > information that is protected by federal law. If you have received this > communication in error, please notify us immediately by telephone and > destroy (shred) the original message and all attachments. Any review, > dissemination, distribution or copying of this message by any person other > than the intended recipient(s) or their authorized agents is strictly > prohibited. Thank you. > -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A & T State University Greensboro, NC 336 334 7717 x2251 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
