On 11/08/12 at 07:04am, Tom Rand wrote:

On Tue, Nov 06, 2012 at 01:16:43PM -0500, David Rosenstrauch wrote:

...

I recently switched over to systemd, and am trying to get my system set up the way I like under there. I'm trying to set up qingy on systemd right now, but it doesn't seem to be working properly.

I followed the instructions here:

https://wiki.archlinux.org/index.php/Qingy#Systemd

... and tried to set up qingy on tty6. But that doesn't seem to work. The systemctl command seems to always try to set up qingy on tty1:

[darose@daroselin ~]$ sudo systemctl enable qingy@tty6 ln -s '/usr/lib/systemd/system/qingy@.service' '/etc/systemd/system/getty.target.wants/qingy@tty1.service'

In addition, qingy seems to be freezing on me whenever I try to access it on the tty.

Anyone have any idea what's going on with this? I didn't see any bug reports about it.

Thanks,

DR

I had the same issue so i just went to /etc/systemd/system/getty.target.wants/ & renamed quingy@tty1.service to quingy@tty6.service then it behaved as expected.

Check out the service file for qingy. It is actually aliased to qingy@tty1. So I presume copying it over to /etc/systemd/system and changing that the the tty of your choice would solve that issue. See the bottom of the service file in the [Install] section. % cat qingy@.service cat qingy@.service [Unit] Description=Quingy on %I Documentation=info:qingy ... [Install] Alias=getty.target.wants/qingy@tty1.service Regards, -- Curtis Shimamoto sugar.and.scruffy@gmail.com

On 11/08/12 at 11:42am, David Rosenstrauch wrote:

On 11/08/2012 10:08 AM, Curtis Shimamoto wrote:

...

On 11/08/12 at 07:04am, Tom Rand wrote:

...

I had the same issue so i just went to /etc/systemd/system/getty.target.wants/ & renamed quingy@tty1.service to quingy@tty6.service then it behaved as expected.

Check out the service file for qingy. It is actually aliased to qingy@tty1. So I presume copying it over to /etc/systemd/system and changing that the the tty of your choice would solve that issue.

See the bottom of the service file in the [Install] section.

% cat qingy@.service cat qingy@.service [Unit] Description=Quingy on %I Documentation=info:qingy ...

[Install] Alias=getty.target.wants/qingy@tty1.service

Regards,

Just curious (if you know): what should the service file look like for it to work properly when you issue the systemctl enable command? Should it be: Alias=getty.target.wants/qingy@%I.service ?

Thanks,

DR

Honestly, I am not sure if that is proper, but I see no reason why it should not work. Give it a whirl and see what happens. The worst that could come of it is that you change it back. I think in this case, %i would also work, as the only difference between %I and %i is being escaped and not being escaped (respectively). There appears to be nothing in the systemd.unit man page to indicate that these special substitutions are not universal throughout the unit file. Hope it works! -- Curtis Shimamoto sugar.and.scruffy@gmail.com

On 11/08/12 at 04:00pm, David Rosenstrauch wrote:

Looks like it doesn't:

[darose@daroselin ~]$ sudo systemctl enable qingy@tty6 ln -s '/usr/lib/systemd/system/qingy@.service' '/etc/systemd/system/getty.target.wants/qingy@%I.service'

:-)

Sucks that this doesn't work as advertised. It should be a no-brainer to be able to set up qingy on tty6.

Thanks,

DR

Maybe you could simply remove the alias altogether. I mean, if you are going to change it anyway, what is the difference between having it set via an alias or by your specification after the @? It makes me curious why it would be called qingy@.service rather than simply qingy.service if it is going to insist on being on tty1 either way. -- Curtis Shimamoto sugar.and.scruffy@gmail.com

On Fri, Nov 9, 2012 at 1:35 AM, Curtis Shimamoto wrote:

On 11/08/12 at 04:00pm, David Rosenstrauch wrote:

...

Looks like it doesn't:

[darose@daroselin ~]$ sudo systemctl enable qingy@tty6 ln -s '/usr/lib/systemd/system/qingy@.service' '/etc/systemd/system/getty.target.wants/qingy@%I.service'

:-)

Sucks that this doesn't work as advertised. It should be a no-brainer to be able to set up qingy on tty6.

Thanks,

DR

Maybe you could simply remove the alias altogether. I mean, if you are going to change it anyway, what is the difference between having it set via an alias or by your specification after the @?

It makes me curious why it would be called qingy@.service rather than simply qingy.service if it is going to insist on being on tty1 either way.

Hi guys, I'm a bit late to the party, so I'll reply to everything in one go. AFAIK everything is working as advertised and intended, though maybe not as expected. To sum up, "systemctl enable foo.service" has the effect of looking for an [Install] section in foo.service and for every Alias= creating a symlink by that name to foo.service and for every WantBy=bas.target creating a symlink bas.target.wants/foo.service to foo.service. In this particular case it means that "systemctl enable qingy@.service" will create a symlink from getty.target.wants/qingy@tty1.service to qingy@.service. Contrary to what one might reasonably expect there is not yet a special treatment of service templates/instances so, as you have observed, "systemctl enable qingy@tty6.service" does not work. I have heard talk of improving this, but as far as I know nothing has yet come of it. It should be straight-forward to do the right thing: when a service instance is enabled, the WantedBy information should be looked up in the template. So if anyone is looking for an easy patch to get involved with systemd, this is your chance ;-) Cheers, Tom