If you are not finding the appropriate file are you sure you are using the KDM window manager.

I can find it on my system and I have these two items loaded via GSlapt. kdm-small 3.5.5-i586-2vl58 and kdmtheme-Bela 1-noarch-2vl59

To be honest I never chose to switch to the KDM window manager it just seemed to happen when I loaded Amarok. (because Amarok pulls in kdebase)

Just to be sure I was not sending you on a wild goose chase I did it myself.

Using Super File Manager I followed the path above and opened kdmrc in mousepad.I removed the # before the AutoLoginEnable=truethen I entered the two other lines below that one, inserting my own user name.AutoLoginUser= <-- insert user namePreselectUser= <-- insert user nameThen I saved.Restarted my machine to see what would happen and, baddabing, it worked.

Let me know if it is as simple as putting your tightvnc server into autostarted applications after that.

To be honest I never chose to switch to the KDM window manager it just seemed to happen when I loaded Amarok. (because Amarok pulls in kdebase)

Actually, no, it has nothing to do with Amarok. Also, KDM Is NOT a window manager. It is a display manager that controls graphical login and nothing more. kdm-small is the default display manager that is part of every install of Vector Linux. You can't install VL with X without getting kdm installed.

Your window manager in Xfce is Xfwm.

Let's try to keep terminology straight so that we don't confuse people, OK?

I just cought on to this thread... so excuse me if i'm stating something that's already been said.

If this is a local LAN (like your home network), you may be better off with X over ssh.Edit your /etc/ssh/sshd_config and find the line that says "#X11Forwarding no" and change it to read "X11Forwarding yes"then ssh your box from the remote box like this

He's trying to run a headless server -- no monitor, no login, no WM. I don't have the time to install TightVNC and figure this out for him but an rc script is the correct answer. I suspect he needs more than just "vncserver" to make it run in the background or as a daemon but without it installed to test I have no way to check.

You have an eagle eye. That was my mistake. I left out a space. It is working now.

I can power up any of my computers using wake on lan and work on them from any computer with a display. That means I can now access any one of 5 computers, using different operating systems, and see each of thier desktops, run their apps, transfer files, and administrate changes remotely from my laptop. I can use the VNC Viewer or just type their ip address in my browser. It is interesting to note that the Vector machine produces the a more clear and crisp display on the remote ( Windows) machine then any of the remote Windows boxes. Probably due to the way vnc can handle X-Windows in Linux.

By the way, the command I used in rc.local was ...

su - phreon -c "/usr/bin/vncserver" &

I looked up the man page for "su" and it did not have an explanation of "- username" switch. I am guessing it allows the named user to do whatever follows the the - username switch as root and then reverts back to regular user.

The - and the username aren't a switch. The isolated dash tells su to retain the existing environment. The username tells su which user to become. The -c is a switch, which tells su to execute the command that follows. It is in the su manpage.