When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
On Thu, 2007-12-06 at 16:34 -0500, Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
---- I don't recall there being an issue vs runlevel 3 or 5
First off, nx is a much better way to go
Anyway...what's contents of /etc/sysconfig/vncserver ? Is it configured?
Craig
Craig White wrote:
On Thu, 2007-12-06 at 16:34 -0500, Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
I don't recall there being an issue vs runlevel 3 or 5
First off, nx is a much better way to go
yeah, but that will take a bit of work. At least when I look at it back in the summer, it was not just a drop in as vnc has ALMOST been.
Anyway...what's contents of /etc/sysconfig/vncserver ? Is it configured?
Only thing I have configured is the vncservers= line
and for ~/.vnc I have run vncpasswd to set the password and edited the xstartup file to run gnome instead of X:
For Gnome, replace "twm &" with "exec gnome-session &"
also uncommented the two lines in xstartup for 'normal desktop'. Didn't notice any difference though,
Craig
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2007-12-06 at 17:11 -0500, Robert Moskowitz wrote:
Craig White wrote:
On Thu, 2007-12-06 at 16:34 -0500, Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
I don't recall there being an issue vs runlevel 3 or 5
First off, nx is a much better way to go
yeah, but that will take a bit of work. At least when I look at it back in the summer, it was not just a drop in as vnc has ALMOST been.
Anyway...what's contents of /etc/sysconfig/vncserver ? Is it configured?
Only thing I have configured is the vncservers= line
and for ~/.vnc I have run vncpasswd to set the password and edited the xstartup file to run gnome instead of X:
For Gnome, replace "twm &" with "exec gnome-session &"
also uncommented the two lines in xstartup for 'normal desktop'. Didn't notice any difference though,
---- service vncserver restart should be all that you need then
Craig
Craig White wrote:
On Thu, 2007-12-06 at 17:11 -0500, Robert Moskowitz wrote:
Craig White wrote:
On Thu, 2007-12-06 at 16:34 -0500, Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
I don't recall there being an issue vs runlevel 3 or 5
First off, nx is a much better way to go
yeah, but that will take a bit of work. At least when I look at it back in the summer, it was not just a drop in as vnc has ALMOST been.
Anyway...what's contents of /etc/sysconfig/vncserver ? Is it configured?
Only thing I have configured is the vncservers= line
and for ~/.vnc I have run vncpasswd to set the password and edited the xstartup file to run gnome instead of X:
For Gnome, replace "twm &" with "exec gnome-session &"
also uncommented the two lines in xstartup for 'normal desktop'. Didn't notice any difference though,
service vncserver restart should be all that you need then
And how do I do that without logging into the console? My goal is I boot the system up, and then over the network I remote into the server. I suppose I could 'cheat' and have webmin running....
On Thu, 2007-12-06 at 18:10 -0500, Robert Moskowitz wrote:
Craig White wrote:
On Thu, 2007-12-06 at 17:11 -0500, Robert Moskowitz wrote:
Craig White wrote:
On Thu, 2007-12-06 at 16:34 -0500, Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
I don't recall there being an issue vs runlevel 3 or 5
First off, nx is a much better way to go
yeah, but that will take a bit of work. At least when I look at it back in the summer, it was not just a drop in as vnc has ALMOST been.
Anyway...what's contents of /etc/sysconfig/vncserver ? Is it configured?
Only thing I have configured is the vncservers= line
and for ~/.vnc I have run vncpasswd to set the password and edited the xstartup file to run gnome instead of X:
For Gnome, replace "twm &" with "exec gnome-session &"
also uncommented the two lines in xstartup for 'normal desktop'. Didn't notice any difference though,
service vncserver restart should be all that you need then
And how do I do that without logging into the console? My goal is I boot the system up, and then over the network I remote into the server. I suppose I could 'cheat' and have webmin running....
---- you issue 'service vncserver restart' command from any command line (i.e. ssh)
VNC does not have any encryption built in so remember, if you are using over any network, your login/passwords/traffic are not encrypted.
FreeNX handles all that for you PLUS it gives you really nice data compression (better performance over limited bandwidth).
Craig
Craig White wrote:
On Thu, 2007-12-06 at 18:10 -0500, Robert Moskowitz wrote:
Craig White wrote:
On Thu, 2007-12-06 at 17:11 -0500, Robert Moskowitz wrote:
Craig White wrote:
On Thu, 2007-12-06 at 16:34 -0500, Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
I don't recall there being an issue vs runlevel 3 or 5
First off, nx is a much better way to go
yeah, but that will take a bit of work. At least when I look at it back in the summer, it was not just a drop in as vnc has ALMOST been.
Anyway...what's contents of /etc/sysconfig/vncserver ? Is it configured?
Only thing I have configured is the vncservers= line
and for ~/.vnc I have run vncpasswd to set the password and edited the xstartup file to run gnome instead of X:
For Gnome, replace "twm &" with "exec gnome-session &"
also uncommented the two lines in xstartup for 'normal desktop'. Didn't notice any difference though,
service vncserver restart should be all that you need then
And how do I do that without logging into the console? My goal is I boot the system up, and then over the network I remote into the server. I suppose I could 'cheat' and have webmin running....
you issue 'service vncserver restart' command from any command line (i.e. ssh)
I see, of course sshd is running, so I can ssh in, restart vncserver then run vnc client. Kind of cludgy, as why is vncserver NOT starting at boot?
VNC does not have any encryption built in so remember, if you are using over any network, your login/passwords/traffic are not encrypted.
'They' tell you to run vnc at localhost, and ssh tunnel for the security. But one senario of use has the server connected to the client via a crossover cable, so I am not concerned about packet sniffing!
FreeNX handles all that for you PLUS it gives you really nice data compression (better performance over limited bandwidth).
I will be getting back to FreeNX. I am SOOO far behind on SOOO many projects. I just needed some remote login working right now already.
on 12/6/2007 3:10 PM Robert Moskowitz spake the following:
Craig White wrote:
On Thu, 2007-12-06 at 17:11 -0500, Robert Moskowitz wrote:
Craig White wrote:
On Thu, 2007-12-06 at 16:34 -0500, Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
I don't recall there being an issue vs runlevel 3 or 5
First off, nx is a much better way to go
yeah, but that will take a bit of work. At least when I look at it back in the summer, it was not just a drop in as vnc has ALMOST been.
Anyway...what's contents of /etc/sysconfig/vncserver ? Is it configured?
Only thing I have configured is the vncservers= line
and for ~/.vnc I have run vncpasswd to set the password and edited the xstartup file to run gnome instead of X:
For Gnome, replace "twm &" with "exec gnome-session &"
also uncommented the two lines in xstartup for 'normal desktop'. Didn't notice any difference though,
service vncserver restart should be all that you need then
And how do I do that without logging into the console? My goal is I boot the system up, and then over the network I remote into the server. I suppose I could 'cheat' and have webmin running....
"chkconfig vncserver --list" should tell you if it is set to start at runlevel 3, and "chkconfig vncserver on" should make it start on boot at level 3, 4 and 5.
Scott Silva wrote:
on 12/6/2007 3:10 PM Robert Moskowitz spake the following:
Craig White wrote:
On Thu, 2007-12-06 at 17:11 -0500, Robert Moskowitz wrote:
Craig White wrote:
On Thu, 2007-12-06 at 16:34 -0500, Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
I don't recall there being an issue vs runlevel 3 or 5
First off, nx is a much better way to go
yeah, but that will take a bit of work. At least when I look at it back in the summer, it was not just a drop in as vnc has ALMOST been.
Anyway...what's contents of /etc/sysconfig/vncserver ? Is it configured?
Only thing I have configured is the vncservers= line
and for ~/.vnc I have run vncpasswd to set the password and edited the xstartup file to run gnome instead of X:
For Gnome, replace "twm &" with "exec gnome-session &"
also uncommented the two lines in xstartup for 'normal desktop'. Didn't notice any difference though,
service vncserver restart should be all that you need then
And how do I do that without logging into the console? My goal is I boot the system up, and then over the network I remote into the server. I suppose I could 'cheat' and have webmin running....
"chkconfig vncserver --list" should tell you if it is set to start at runlevel 3, and "chkconfig vncserver on" should make it start on boot at level 3, 4 and 5.
OK. --list showed only 5:on, doing the chkconfig vncserver on turned 2-4 on as well. So I will reboot the box and see how it runs!
Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
coming in late, but for next time: system-config-services shows just one runlevel by default, probably 5, you have to select "runlevel all" (or just runlevel 3) in the "Edit runlevel" menu
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
Nicolas Thierry-Mieg wrote:
Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
coming in late, but for next time: system-config-services shows just one runlevel by default, probably 5, you have to select "runlevel all" (or just runlevel 3) in the "Edit runlevel" menu
oh.
Well the box is now running head/kybd/mouseless, at init 3, and I am in looking at a gnome desktop.
I can make notes from all the other responses, get on with work at hand and later go back to get a 'better' remote console tool. But one advantage of vnc is how fast I configured it; on an install, I can be hooked to a head/kybd/mouse, quickly get vnc working, move the system, then work on whatever else is needed (including installing a better remote console tool).
I log in on the console as root and
service vncserver start
and it starts with some warning messages about bad display name in "add" command, but I do not see where these are logged to copy them into this message.
Once I start it from the console, I have trouble using the vnc client to access the server.
I really need for the vncserver to start at boot, as I want it to run in a place with no monitor or keyboard....
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
on 12/7/2007 5:26 AM Robert Moskowitz spake the following:
Nicolas Thierry-Mieg wrote:
Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
coming in late, but for next time: system-config-services shows just one runlevel by default, probably 5, you have to select "runlevel all" (or just runlevel 3) in the "Edit runlevel" menu
oh.
Well the box is now running head/kybd/mouseless, at init 3, and I am in looking at a gnome desktop.
I can make notes from all the other responses, get on with work at hand and later go back to get a 'better' remote console tool. But one advantage of vnc is how fast I configured it; on an install, I can be hooked to a head/kybd/mouse, quickly get vnc working, move the system, then work on whatever else is needed (including installing a better remote console tool).
Vnc is fine for local net admin. You are just advised to not allow its use over unsecured links like the internet without point-to-point encryption like an ssh tunnel or vpn. But you really should take some time to learn ssh/commandline tools for those times you have no other access. Some configuration tasks can only be done that way, because the GUI tools are only so sophisticated. They are great for a quick fix, but there will always be something they can't do.
Scott Silva wrote:
on 12/7/2007 5:26 AM Robert Moskowitz spake the following:
Nicolas Thierry-Mieg wrote:
Robert Moskowitz wrote:
When I run system-config-services, it shows vncserver set to start at boot.
in /etc/inittab I have init 3
vncserver does not start at boot.
coming in late, but for next time: system-config-services shows just one runlevel by default, probably 5, you have to select "runlevel all" (or just runlevel 3) in the "Edit runlevel" menu
oh.
Well the box is now running head/kybd/mouseless, at init 3, and I am in looking at a gnome desktop.
I can make notes from all the other responses, get on with work at hand and later go back to get a 'better' remote console tool. But one advantage of vnc is how fast I configured it; on an install, I can be hooked to a head/kybd/mouse, quickly get vnc working, move the system, then work on whatever else is needed (including installing a better remote console tool).
Vnc is fine for local net admin. You are just advised to not allow its use over unsecured links like the internet without point-to-point encryption like an ssh tunnel or vpn. But you really should take some time to learn ssh/commandline tools for those times you have no other access. Some configuration tasks can only be done that way, because the GUI tools are only so sophisticated. They are great for a quick fix, but there will always be something they can't do.
I have been using SSH pretty much since the gang over in Finland wrote it. I first met Tatu Ylonen when I was running the IPsec interop workshops.
But here I have a different goal. I am working on remote graphic apps.
-
Craig White -
Nicolas Thierry-Mieg -
Robert Moskowitz -
Scott Silva