On 11/10/18 9:00 PM, Ed Greshko wrote:
On 11/11/18 12:48 PM, ToddAndMargo via users wrote:
That is a good workaround. Or just wait for the Xfce Policy Kit to prompt.
But they should be able to be started under certain conditions
by regular users Saned for instance.
I've not used that service. But, 2 things....
I don't know who your users are, but you may not want to give them blanket privileges to
run systemctl
Is the service a "resource hog" such that it will impact system performance if it is just
started normally at boot?
If you try to set it up to start at boot, you get:
# systemctl enable geoclue
The unit files have no installation config (WantedBy, RequiredBy, Also,
Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
So it is suppose to fire up and die.
I that with saned, that you can give certain services start up rights
to users
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
