Re: Systemd migration: opinion and questions

Marc Joliet posted on Tue, 24 Feb 2015 21:15:45 +0100 as excerpted:

> I would like to convert some programs I start in .xprofile to units that
> are started by my users's systemd instance.  I started off with mpd,

It looks like you got this sorted, but FWIW...

I just use the standard system level mpd.service here.  It drops privs 
and runs as its own user, and it listens localhost for connections from 
clients run as normal users, which pretty well limits any potential 
security issues, and that means I can control it via either my normal X 
user and GUI client, or mpc or whatever as either my normal user or my 
admin user (or root, for that matter).

In fact, IMO that's mpd's biggest advantage over most other players.  I 
don't have to be in X to play music, and in fact, I can not only quit X, 
but log out as the user I started playing the music with, and have it 
continue uninterrupted, controlling it when I need to using mpc from 
whatever other user (here, normally my admin user).

IOW, I really do use it as the system service/daemon that the name, mpd, 
music player daemon, implies. 

And as such, I don't /want/ to start it from user login or service, I 
want it as a system service, which is how I run it. =:^)

But you're king of your own boxes.  If you want to run it as a user-level 
service and have it quit when you logout that user, go right ahead.  
Don't let the fact that such usage bothers me and I don't see the point, 
if you're running it as your normal user anyway, there's all those other 
player apps, why use mpd in that case, bother you.  (No, that isn't 
sarcasm.  Yes, it does bother me, but it's your box and your choice, and 
presuming to take that away from you would bother me **FAR** more.  So do 
it the way that works best for you! =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman