David, Seth's suggest of using ssh as a low-level terminal interface is relevant here. I reproduce what he said:
Curt, Here is another possible workaround. I've haven't used it specifically for VNC, but I have used it for situations where I needed to get into an NT box remotely to stop some process. The latest release of the cygnus windows tools (www.cygwin.com) includes a windows side server for ssh (and sftp, etc.) I make an ssh connection to the windows box and do whatever is necessary (in your case stopping and restarting VNC). This isn't a fix, but it can be used until a fix is available. ... Seth David W. Chapman Jr. wrote: > > I'm not sure where to put this so I will ask here. Would it be > possible for there to be an option while doing remote upgrade to > stop the tightvnc service and then install vnc and then start the > service back again once the proper files are installed? > > -- > David W. Chapman Jr. > [EMAIL PROTECTED] Raintree Network Services, Inc. <www.inethouston.net> > [EMAIL PROTECTED] FreeBSD Committer <www.FreeBSD.org> > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list -- W. Curtiss Priest, Director, CITS Center for Information, Technology & Society 466 Pleasant St., Melrose, MA 02176 Voice: 781-662-4044 [EMAIL PROTECTED] Fax: 781-662-6882 WWW: http://Cybertrails.org _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
