New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate PolicyKit agent from shell #146
Comments
plfiorini
added a commit
that referenced
this issue
Feb 25, 2014
Move the code to a separate process. It doesn't build now and will be fixed later. Issue: #146
plfiorini
added a commit
that referenced
this issue
Feb 25, 2014
plfiorini
added a commit
that referenced
this issue
Feb 25, 2014
With the PolicyKit agent being a separate process we can allow people building this module without it. Issue: #146
plfiorini
added a commit
that referenced
this issue
Feb 25, 2014
We only have one instance of it anyway. Issue: #146
plfiorini
added a commit
that referenced
this issue
Feb 25, 2014
Notify systemd upon startup. Issue: #146
plfiorini
added a commit
that referenced
this issue
Feb 25, 2014
Make it work outside the shell. Issue: #146
plfiorini
added a commit
that referenced
this issue
Feb 25, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PolicyKit agent should be a separate executable just like we did for the notifications daemon.
The text was updated successfully, but these errors were encountered: