Bug 69228 - vnc init.d script start portion is broken in respect of the "cd" command
vnc init.d script start portion is broken in respect of the "cd" command
Product: Red Hat Linux
Classification: Retired
Component: vnc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-07-19 06:23 EDT by Alexander Stohr
Modified: 2007-04-18 12:44 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-07-19 07:48:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexander Stohr 2002-07-19 06:23:19 EDT
Description of Problem:
The file  /etc/init.d/vncserver is broken and does not work as desired.

Version-Release number of selected component (if applicable):
does not apply

How Reproducible:

Steps to Reproduce:
1. log in as a local user, launch vncserver, specify password, test, kill server afterwards
2. add a line to /etc/sysconfig/vncservers for the above user like this: VNCSERVERS="1:username"
3. launch /etc/init.d/vncserver with start and stop options to test config

Actual Results:
the vnc server wont launch

Expected Results:
the vnc server should launch

Additional Information:
the parameter for the "cd" command in the start/stop script is odd.
it is "~/$...something" but it should be only "~".

Btw. the description in the header of the sysconfig file is a bit unprecise.
the requirement is: the password for the server must be set just once to run.
If its done via vncpasswd or alternatively by trying out the server manually 
is not important.
Comment 1 Tim Waugh 2002-07-19 07:48:50 EDT
The cd parameter is (in your case) ~username, which is correct.

Please check that the script is as shipped using 'rpm -V vnc-server'.
Comment 2 Tim Waugh 2002-07-19 09:18:56 EDT
Closing (discussed in private mail).

Note You need to log in before you can comment on or make changes to this bug.