From: "Ian Manners" <ecs-isp@2rosenthals.com>
Message-ID: <100.80ea0d0071376c65.003@os2site.com>
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
Date: Sun, 03 Dec 2023 16:08:17 +0800 (AWS)
In-Reply-To: <list-8670776@2rosenthals.com>
References: <list-8670775@2rosenthals.com>
  <list-8670776@2rosenthals.com>
Priority: Normal
User-Agent: PMMail/3.11 (os/2; U; Warp 4.5; en-AU; i386; ver 3.11.47.2052)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [eCS-ISP] VNC

Hi Peter,

Adding to what others have mentioned.

Important to head a monitor around for those times you
need to put a head on your headless server :)

Every few years when my server has stopped for some reason,
looking at the screen has been important, first thing I've done
for unexpected things is to clean out the dust and check items
like thermal paste are still ok on the heatsink, reseat any PCI
cards (two NIC's) and replug leads etc. I also developed a
habit of using electrically safe contact grease.

Both the old PMVNC and Andrey's VNC have been rock solid
for me while I used them. I've only turned my server on maybe
once this year, which is a shame but yep.

Cheers
Ian Manners

On Sat, 02 Dec 2023 22:50:32 -0800 Steven Levine wrote:
> 
> In <list-8670775@2rosenthals.com>, on 12/03/23
>    at 05:27 PM, "Peter Moylan" <ecs-isp@2rosenthals.com> said:
> 
> Hi Peter,
> 
> >I use VNC to look at my server computer from my desktop computer.
> 
> Which VNC implementation are you using=3F  I've been switching over to
> Andrey's VNC implemenation as time permits.  It does a lot of things
> better than the circa 2004 PMVNC.
> 
> I'm a keyboard guy, so for some things the legacy pmvnc offers better
> keyboard access.  However, I need to do some more information gathering=

> before I am ready to discuss this with Andrey.
> 
> >In some other situations, I want to kill one version of a program and
> >start another version. So far I haven't managed to find a command-line=

> >"kill process" utility that will work across the LAN, so VNC is the on=
ly
> >way I have to do that.
> 
> All the remote methods I know of require running an agent on he server.=
 
> If you are going to do this, you might as well use VNC or telnet.
> 
> >Lately the VNC server seems to crashing overnight (or perhaps just
> >failing to respond). The only solution I've found is to reboot the
> >server.
> 
> I need a bit more information before I can offer any possibly useful
> suggestions.  First, which VNC=3F  Second are you getting popuplog type=

> crashes or stuck in the exit list type crashes or something else=3F
> 
> >Is this a known problem=3F
> 
> Not to my knowledge.  Both VNC implementations are very stable.  I cann=
ot
> recall the last time either VNC crashed on me.
> 
> Since the problem seems to be recent, you might try to think of what mi=
ght
> have changed at about the same time the problems started.
> 
> Steven
>