Bug 1662306

Summary:	TigerVNC Configuration Page out of date
Product:	[Fedora] Fedora Documentation	Reporter:	Colin Henry <colin.henry>
Component:	system-administrator's-guide	Assignee:	Petr Bokoc <pbokoc>
Status:	NEW ---	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	swadeley
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Colin Henry 2018-12-27 14:39:07 UTC

Description of problem:

Documentation does not reflect current file configuration

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

Fedora 29

How reproducible:
Try and follow the instructions on the configuration page, it tells you to change settings that aren't there. For instance, users are told to edit the 

and change:

ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024"
PIDFile=/home/USER/.vnc/%H%i.pid

Whereas the actual file contains:

ExecStart=/usr/bin/vncserver -autokill %i
PIDFile=/home/<USER>/.vnc/%H%i.pid

Steps to Reproduce:
1. Go to the documentation page: https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/infrastructure-services/TigerVNC/
2. Install tigervnc-server
3. Look at the configuration file /lib/systemd/system/vncserver@.service

Actual results:
The files differ significantly, also following the instructions in the configuration file fails to start vnc successfully, but I'll file a bug for that separately.

Expected results:
Configuration documentation should match the files on the host

Additional info: