On Fri, 30 Nov 2001, Go, Jeffrey wrote:
> Hi jerry
>
> Can I ask a neophyte's stupid question?..
>
> I go to my /etc file and see about 3 rc.d files...mainly rc0.d, rc1.d and
> rc3.d
>
> How would I add or what command would I use to add the VNCserver there?
>
>
Jeff,
The directory that counts is /etc/rc.d not rcN.d (N=0,1,2,3,...)
and in particular, the init.d subdirectory of rc.d
But you don't want to make entries in there by hand if you don't have to
(you could if you absolutely had to, and that is one of the GOOD THINGS
about Linux, you can do things by hand if you have to)
Are you saying that vncserver does NOT show up in the output of
chkconfig --list ?
Usually, when a daemon service package is installed, it puts
entries in /etc/rc.d/init.d In particular, it puts a little shell script
that directory to start up the daemon (this script knows where the real
program binary is). Symbolic links are also set up.
Using chkconfig is the clean way to do this. However, if your
installation of vncserver did not provide this nice set up, then there is
another way to cause services to start up when you system starts up:
YOu can put an entry in /etc/rc.d/rc.local
This is a shell script that is designed for your own "local" scripts to be
run after all the usual "redhat provided" system startup scripts run (the
rc3.d or rc5.d scripts are run when you enter that run level. level 5 is
multi-user, with X-Windows running; run level 3 is just multi-user, no X.)
If you edit /etc/rc.d/rc.local, you can always put an entry in there that
simply starts vncserver "by hand", if that is indeed what you want to do.
Note, however, that since entries have not been made in /etc/rc.d/init.d
for vncserver, in this case, that the service command to start/stop
vncserver would not work. But, since you've got it started by rc.local,
you don't need.
> -----Original Message-----
> From: Jerry Winegarden [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 30, 2001 8: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
