running vncserver via systemctl on Fedora 20

[Robert Moskowitz]

I have run vncserver for years, naturally as 'service vncserver start'.  
But now it is all systemd and systemctl.  Fine.  So I think I have to 
configure it for my user, as I always use to edit 
/etc/sysconfig/vncserver with:

VNCSERVERS="2:alice 3:bob"

So I found I had to:

cp /lib/systemd/system/vncserver@.service 
/etc/systemd/system/vncserver@.service

but I could not figure out what I needed to edit in this file.  So I 
tried to start the service with:

systemctl start vncserver

And got:

Failed to issue method call: Unit vncserver.service failed to load: No 
such file or directory.

So what am I missing?

Also in ~/.vnc/xstartup I changed the execute to:

exec gnome-session &

But the xstartup is created the first time I would start the server...

So things are really working differently and I would appreciate some 
pointers.

thanks

[Robert Moskowitz]

I am making some headway.  My normally weak search foo came up with

http://zeusville.wordpress.com/2012/01/27/setting-up-vncserver-on-fedora-16/

Still almost as confusing as I started.  Particularly if I want more 
than one userid to be able to use vncserver.

On 07/21/2014 03:33 PM, Robert Moskowitz wrote:
> I have run vncserver for years, naturally as 'service vncserver 
> start'.  But now it is all systemd and systemctl.  Fine.  So I think I 
> have to configure it for my user, as I always use to edit 
> /etc/sysconfig/vncserver with:
>
> VNCSERVERS="2:alice 3:bob"
>
> So I found I had to:
>
> cp /lib/systemd/system/vncserver@.service 
> /etc/systemd/system/vncserver@.service
>
> but I could not figure out what I needed to edit in this file.  So I 
> tried to start the service with:
>
> systemctl start vncserver
>
> And got:
>
> Failed to issue method call: Unit vncserver.service failed to load: No 
> such file or directory.
>
> So what am I missing?
>
> Also in ~/.vnc/xstartup I changed the execute to:
>
> exec gnome-session &
>
> But the xstartup is created the first time I would start the server...
>
> So things are really working differently and I would appreciate some 
> pointers.
>
> thanks

[Michael D. Setzer II]

On 21 Jul 2014 at 15:33, Robert Moskowitz wrote:

Date sent:      	Mon, 21 Jul 2014 15:33:39 -0400
From:           	Robert Moskowitz 
To:             	[e-mail]
Subject:        	running vncserver via systemctl on Fedora 20
Send reply to:  	Community support for Fedora users 

    

    
> I have run vncserver for years, naturally as 'service vncserver
> start'.  But now it is all systemd and systemctl.  Fine.  So I think I
> have to configure it for my user, as I always use to edit
> /etc/sysconfig/vncserver with:
>
> VNCSERVERS="2:alice 3:bob"
>
> So I found I had to:
>
> cp /lib/systemd/system/vncserver@.service 
> /etc/systemd/system/vncserver@.service
>
> but I could not figure out what I needed to edit in this file.  So I
> tried to start the service with:
>
> systemctl start vncserver
>
> And got:
>
> Failed to issue method call: Unit vncserver.service failed to load: No
> such file or directory.
>
> So what am I missing?
>
> Also in ~/.vnc/xstartup I changed the execute to:
>
> exec gnome-session &
>
> But the xstartup is created the first time I would start the server...
>
> So things are really working differently and I would appreciate some
> pointers.
>
> thanks

I found it easier to user rc.local to start the sessions 
runuser -l user -c 'vncserver :port geometry 1280x1024'
where user is the user id, and port is the port you want to user it on.
The systemctl requires you to copy the file with the :port added, and then you 
have to modify it with the users name.

I also tried running boinc via systemctl, and it would start, but they would only 
run at about 33% of the cpu, whereas running them directly would use 98% 
or higher.

You do have to create the /etc/rc.d/rc.local file, and make sure the service is 
running, since it isn't by default.
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have
> a question? Ask away: http://ask.fedoraproject.org

+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:[e-mail]                            
  mailto:[e-mail]
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
ROSETTA     17875371.077265   |   SETI        29536891.845165
ABC         16613838.513356   |   EINSTEIN    28547237.391636

[Ed Greshko]

On 07/22/14 03:33, Robert Moskowitz wrote:
> I have run vncserver for years, naturally as 'service vncserver start'.  But now it is all systemd and systemctl.  Fine.  So I think I have to configure it for my user, as I always use to edit /etc/sysconfig/vncserver with:
>
> VNCSERVERS="2:alice 3:bob"
>
> So I found I had to:
>
> cp /lib/systemd/system/vncserver@.service /etc/systemd/system/vncserver@.service
>
> but I could not figure out what I needed to edit in this file.  So I tried to start the service with:
>
> systemctl start vncserver
>
> And got:
>
> Failed to issue method call: Unit vncserver.service failed to load: No such file or directory.
>
> So what am I missing?
>
> Also in ~/.vnc/xstartup I changed the execute to:
>
> exec gnome-session &
>
> But the xstartup is created the first time I would start the server...
>
> So things are really working differently and I would appreciate some pointers.
>
> thanks

First of all....   If you have a fresh install of F18(maybe F17) and above you'd find....

[root@f20f sysconfig]# cat /etc/sysconfig/vncservers
# THIS FILE HAS BEEN REPLACED BY /lib/systemd/system/vncserver@.service

The point being, that file isn't used any longer.

Have you tried simply following the instructions in /lib/systemd/system/vncserver@.service ?

# Quick HowTo:
# 1. Copy this file to /etc/systemd/system/vncserver@.service
# 2. Edit <USER> and vncserver parameters appropriately
#   ("runuser -l <USER> -c /usr/bin/vncserver %i -arg1 -arg2")
# 3. Run `systemctl daemon-reload`
# 4. Run `systemctl enable vncserver@:<display>.service`

Works for me....

Now, you'll have to multiple unique /etc/systemd/system/vncserver files to enable different users and ports.