When Fedora 15 rocked up it brought with it a replacement for the old init-style startup called systemd. In Fedora 15, it was pretty easy to ignore this change as everything (including vncserver) ran pretty much the same as before.
Fedora 16 is a little more “aggressive” about it’s use of systemd. When you issue and old-style service command, you are in no doubt that things have changed.
[root@homer system]# service nfs stop Redirecting to /bin/systemctl stop nfs.service [root@homer system]#
Once again, not a big deal in itself.
So that brings me to the reason for this post. The configuration of VNC Server has changed completely between Fedora 15 and Fedora 16. By default you can’t get away with editing the “/etc/sysconfig/vncservers” file anymore. That issue prompted me to knock up a quick article to remind myself how to do the systemd-style setup.
I included the old method for the sake of comparison.
3 thoughts on “Configuring VNC Server on Fedora 16…”
Thanks for the article. I had a question for you. I setup VNCserver properly and connectivity to my box works; however, the service always stops after three days. I’m using Fedora 17, 64-bit. Have you encountered that issue?
@Sodo: Sorry. I’ve not seen this before. 🙁
Thanks anyway, Tim.
Comments are closed.