Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 510261 [details]
Native systemd service file for vncserver
I should point out that if you want to run this as a different user you ( as an admin ) would do the following
# cp /lib/systemd/system/vncserver.service /etc/systemd/system
# sed -i 's/root/myusername/g' /etc/systemd/system/vncserver.service
# systemctl daemon-reload
# systemctl start vncserver.service
Created attachment 510435 [details]
Patch that Introduce systemd unit file, drop SysV support to the spec file..
Ping what's the current status of this ?
What's the current status of this you are the only one that has not package
native systemd unit files in the Base-X group
If you dont have the time to look at the unit file and package it should I try to find a proven packager to do this for you?
Sorry for late response, I was busy with other urgent duties.
Your systemd unit file looks fine for me, thanks for it. There is one remaining question - about backward support of the sysconfig configuration. I raised question on devel list (http://lists.fedoraproject.org/pipermail/devel/2011-July/154587.html).
(In reply to comment #6)
> Sorry for late response, I was busy with other urgent duties.
If you are reletively busy and have more daemons/service you mantain we could schedual a converting day which we would try to get them all done that same day you would just provide me with a list of those daemons/service and I could perform initial convertion of them then we could just use the day to walk through them and iron out any issues we might encounter.
> Your systemd unit file looks fine for me, thanks for it. There is one remaining
> question - about backward support of the sysconfig configuration. I raised
> question on devel list
OH I'm pretty sure the backward capability is out.
And from the looks of it I'm not sure if we can achive something similar of what is done there using a template and spawning a vncserver for each user account or when a user would try to connect or something atleast that probably would require some work in vncserver code. ( the idea being that the admin would just have to edit one template for all users ).
I think you should just ship the unit file as is then go for the a) Lennart suggest on that thread I'm not seeing the benefits b) brings as opposed the admin simply does what I suggested in comment 2
I like Lennart's solution b) - to create simple "/usr/lib/vnc/start-vnc-instance" script and then create proper vncserver@.service links. In this approach we can have centralized configuration of all Xvnc servers in sysconfig/vncservers and good backward compatibility.
I will create the script later today.
Will this be ready for thursday?
(In reply to comment #10)
> Will this be ready for thursday?
Yes, it will be ready in next 2 hours...
I just commited http://pkgs.fedoraproject.org/gitweb/?p=tigervnc.git;a=commit;h=9956c17c57d2ce920b8f8f9985c05a0ceebde20a so tigervnc-1.0.90-6.fc16 should be systemd ready.
tigervnc-1.0.90-6.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tigervnc-1.0.90-6.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
tigervnc-1.0.90-6.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.