Properly name filehandle based on context of code

Old harmless copy/paste from code above left code confusing as it was reusing the filehandle "XSTARTUP" to write out $vncUserDir/config. This new small change uses a more topical filehandle name for the task at hand.

diff --git a/unix/vncserver b/unix/vncserver
index bb95506db9ffd251591f9170b8428c4f2446ba09..8f1f4b7c38aee6eb4c652b2c2e40791d430b7fdf 100755 (executable)
--- a/unix/vncserver
+++ b/unix/vncserver
@@ -362,9 +362,9 @@ if (! $skipxstartup) {
 
 if (!(-e "$vncUserDir/config")) {
     warn "Creating default config $vncUserDir/config\n";
-    open(XSTARTUP, ">$vncUserDir/config");
-    print XSTARTUP $defaultConfig;
-    close(XSTARTUP);
+    open(VNCUSERCONFIG, ">$vncUserDir/config");
+    print VNCUSERCONFIG $defaultConfig;
+    close(VNCUSERCONFIG);
     chmod 0644, "$vncUserDir/config";
 }