That script looks to be written in a quite old style of Perl, and it doesn't make use of any standard modules where it could, and could take a lot of clean up work to bring it up to modern standards. Sure, it could be modified*, but it might not hurt to take a step back:
The goal is to avoid using switches when invoking /usr/bin/vncserver
Are you sure that's the easiest solution to the problem (which you haven't described)? It requires you to maintain a patched version of a script you don't fully understand. Why not just write a small wrapper shell script around vncserver?
#!/bin/sh /usr/bin/vncserver -geometry 2000x1200 # ... etc
* Quick & dirty example (requires Config::Tiny):
use Config::Tiny; my $cfg = Config::Tiny->read("$ENV{HOME}/.vnc/config"); $geometry = $cfg->{_}{geometry} if exists $cfg->{_}{geometry};
Just enough rope ;)
In reply to Re: Like to modify /usr/bin/vncserver to parse a config file
by Anonymous Monk
in thread Like to modify /usr/bin/vncserver to parse a config file
by gsky
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |