> OK, fess up time: I went through this whole schmozzle myself > the other day. I ended up doing the following: > > /sbin/chkconfig --levels 2345 vncserver off > /sbin/service vncserver stop > > In other words, killing the service management provided by RH > for Xvnc/vncserver. > > I then just did a simple "vncserver" at my user prompt. It > asked me for a password then the verify, then it forked > itself off in the background as it should and I could connect > at will from my other boxes. Vncserver is now being started > in my /etc/rc.d/local instead of the init.d. Not sure if I > just didn't grok how RH has its vncserver management setup > (highly likely) or if there really is something broken. Yes, > I tried the /etc/sysconfig/vncservers but this didn't work > either. Same symptoms as Vinnie described. > > jb
Ok, so I'm glad it's not just me. I failed to mention this happens on 2 other 7.2 boxes that I have, the exact same behavior, though I'm not worried about using the service manager on them. I know using rc.local isn't such a bad workaround, but what about running a "cleanup" script if the server reboots suddenly? I guess I could just add a line in rc.local just before I call vncserver, like /bin/rm -rf /tmp/.X1-lock /usr/bin/vncserver I just like the service manager, and would like to see it work. Thanks. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
