Yes. All the links are created correctly, vncserver is listed in chkconfig (and is therefore linked in /etc/rc.d/rc5.d, as I have run level 5 as default).
This is not where the problem is, however. I have the service configured to startup (and thus shutdown) correctly. The problem is when RUNNING the script in /etc/rc.d/init.d, it is not correctly starting vncserver, or correctly stopping a running pid. I may have thrown too much information out at once. Here are my basic questions/problems: 1. question: why doesn't the command `service vncserver start` start vncserver, even though it displays the action result "[ok]"? Investigation: -I have run `service vncserver status` after I try to start it (as stated above), and it displays "Xvnc is stopped" -I have checked my process status for vncserver, and I don't see a pid. I used the following method: `ps ax | grep vncserver`. -I have manually executed `vncserver`, which will then start the server properly. -I can then execute `service vncserver status` and it will report a "Xvnc (pid xxx) is running..." -I can also grep my processes (as I did before), and I will see the same pid. Also: For this reason, I cannot rely on the service being listed in chkconfig, as this only ensures there is a link in the proper location for startup and shutdown. The script IS executing properly, it IS NOT starting the server properly. Therefore, I have had to add the entry `/usr/bin/vncserver` in my /etc/rc.d/rc.local to start the server 2. question: why doesn't the command `service vncserver stop` stop a running vncserver, even though it displays the action result "[ok]"? Investigation: -I have run `service vncserver stop` after I manually start a vncserver (as described above), and the action result is "[ok]", but when I run `service vncserver status` (or check ps) the pid is still running. -I can manually kill the server with the command `vncserver -kill :1` and it will stop correctly, and clean up the temp screen in /tmp/.X1-lock Also: This is not a problem, the server stops correctly when I manually kill it, but what happens if the system reboots unexpectedly? I will 3. question: where can I edit what default tcp port vnc uses? Detail: -I am currently reading documentation on how to tunnel through ssh, which is what I would prefer to do on a publicly accessible machine. HOWEVER, I am only using vnc on an internal network, behind a PIX firewall, between protected clients. If I need to access the server from a remote (outside the PIX) location, I vpn via a cisco 3000 concentrator using IPSEC first, then access my vncserver. Also, on my linux box, my iptables rules only allow internal ip address to access only the specific ports I allow (ssh, ftp, and vnc). -In addition, ssh tunneling still uses a tcp port for vnc, and I would like to know where to change this. The vnc documentation seems to point me in circles on where to find out how to change the port. I don't see it in `man vncserver` or any other docs, though I'm sure I'm overlooking something. Thanks. -----Original Message----- From: Jerry Winegarden [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 10:51 AM To: [EMAIL PROTECTED] Subject: Re: Vncserver management On Fri, 30 Nov 2001, Vinny Valdez wrote: > I have a quick question. Has anybody successfully used the vncserver > script in /etc/rc.d/init.d (or `server vncserver start`) on RedHat > 7.2? > > I can execute it, and will get the action feedback: > > Starting VNC server: [ OK ] > > But, a `ps ax | grep vnc` produces no pids. And `serice vncserver > status` reports > > Xvnc is stopped > > However, if I manually run `vncserver` and then run `service vncserver > status` it will give me a pid. I can then connect, using port 5901 (I > remember this from using vnc in the past), and also wondered where to > change this. > > The last thing, is `service vncserver stop` will NOT kill the pid, and > clean up the tmp screen in /tmp/.X1-lock. I have to remove file > manually, or the next server will run on 5902, 5903, etc. > For the automatic startup of service daemons to occur, the proper setup must be done in /etc/rc.d/init.d Use chkconfig to see if this has been done (it is likely it hasn't). chkconfig --list | more look for vncserver. you will want to start it up in at least run states 3 and 5, i would assume. chkconfig --level 345 vncserver on will enable vncserver to be started up automagically. also, the proper links, etc will be set in /etc/rc.d/init.d so that the service command for starting/stopping vncserver can be used (also /etc/rc.d/init.d/vncserver start|stop|restart|status will work) So, does vncserver show up in chkconfig --list ? HTH -- ************************************************************************ *** Jerry Winegarden OIT/Technical Support Duke University [EMAIL PROTECTED] http://www-jerry.oit.duke.edu ************************************************************************ *** _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
