in reply to Like to modify /usr/bin/vncserver to parse a config file

I was thinking along the same lines as Anonymonk above. Here's a little wrapper with example config file that I think should get you close to what you need. I don't know what the actual values for the parameters are supposed to be, nor can I test it. If there is no value after the =, it is considered undef and won't be loaded.

Code:

use warnings; use strict; use Config::Tiny; if (! $ARGV[0]){ print "Usage: $0 servername\n"; } my $server = $ARGV[0]; my $conf = Config::Tiny->read('~/vnc.conf'); my $cmd = "/usr/bin/vncviewer $server "; while (my ($option, $value) = each %{ $conf->{vnc} }){ if (defined $value && $value ne ''){ $cmd .= "$option $value "; } } system($cmd);

Config file:

[vnc] -name = steve -desktop = mine -httpd = 0 -auth = steve -geometry = 640x480 -depth = 1 -pixelformat = -rfbwait = -rfbauth = -rfbport = 5590 -fp = -pn =

Here's the command that would be run by system() when you invoke the script like ./vnc.pl servername:

/usr/bin/vncviewer servername -geometry 640x480 -auth steve -desktop m +ine -httpd 0 -depth 1 -name steve -rfbport 5590

Replies are listed 'Best First'.
Re^2: Like to modify /usr/bin/vncserver to parse a config file
by gsky (Initiate) on Oct 13, 2015 at 15:16 UTC

    Thank you for this contribution. I think it's an elegant way to accomplish the goal. Is it possible to integrate this type of solution into the upstream script I linked such that if ~/.vnc/config exists, that would will invoke Xvnc parsing the file, else use the workflow upstream has setup?

    Again, the goal I should have mentioned in my original post is to have upstream (tigervnc) review and ultimately accept this modification, so I can't implement in a wrapper script as a one-off. Thanks again!