Also be aware that VNC memory requirements are directly related to the graphics resolution you are attempting to use (e.g. W x H x ColorDepth). So if you are trying to run VNC at a resolution like 1600 x 900 x 4 - that is 5,760,000 bytes per-refresh! (the 4 is for 32-bit color depth, 3 for 24-bit and so on) Now many VNCs do a type of frame-defferencing that tries to only repaint changed pixels each refresh to save a bit of memory and bandwidth, but if you are moving windows or trying to run full-screen video, that doesn't help.
Why not just use ssh alone and work from the command line? The only thing you can't do that way is graphic editing, and the zero has no problem running as many simultaneous instances as you like.
If it were ssh alone and you still receive dropouts (say every 5 minutes), then you can set the client ssh ServerAliveInterval and ServerAliveCountMax config parameters to keep the session alive for ever (settings of 300 and 3, respectively will do).
What VNC resolution and color depth are you attempting to use?
Why not just use ssh alone and work from the command line? The only thing you can't do that way is graphic editing, and the zero has no problem running as many simultaneous instances as you like.
If it were ssh alone and you still receive dropouts (say every 5 minutes), then you can set the client ssh ServerAliveInterval and ServerAliveCountMax config parameters to keep the session alive for ever (settings of 300 and 3, respectively will do).
What VNC resolution and color depth are you attempting to use?
Statistics: Posted by drankinatty — Wed May 29, 2024 11:17 pm