top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration
Print Preview

systemd service spawning packagekit daemon

+1 vote
92 views

On Fedora 19, the packagekit daemon runs once in while in the background. Can somebody please inform me about the systemd service that is responsible for spawning the packagekit daemon?

posted Aug 29, 2013 by Sumit Pokharna

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

1 Answer

+1 vote

http://www.packagekit.org/pk-faq.html#system-daemon

rpm -ql PackageKit | grep [.]service
rpm -qf /usr/share/dbus-1/system-services/
rpm -ql dbus | grep [.]service

and for more details, ask these folks http://www.packagekit.org/pk-authors.html

answer Aug 29, 2013 by Ahmed Patel
Similar Questions
+1 vote

I'm running Fedora-24(beta)/KDE, and sendmail/email (through KMail) is failing.
When I try to send email I get the warning "Failed to transmit message", and journalctl has the entry
"sendmail.service: PID file /run/sendmail.pid not readable (yet?)
after start: No such file or directory".

I've checked, and sendmail.pid is in place:

$ sudo cat /run/sendmail.pid 
2829 
/usr/sbin/sendmail -bd -q1h 

Googling for the journalctl entry, I see people have been encountering this problem for years. But I haven't seen any solution offered. Several of the comments suggest that it is a systemd problem.

please help?

+1 vote

What kind of secret voodoo does one need to use rsyslog on a systemd system? Is it even possible?

I have installed it, and I only get kernel boot messages in /var/log/messages.

I find journalctl to be fundamentally braindead, lacking features which we have taken for granted for decades in redhat/rhel/fedora/centos. (Seriously, whats the wisdom of keeping ALL logs around forever?, and in an easily corruptible format).

I found something on the fedora web site which said to just install rsyslog. Which seems to be obsolete or invalid.

0 votes

I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs:

 # systemctl start transmission-daemon.service

If I let it be for a few minutes (~5), it finishes with a failure. The log is extremely unhelpful. This is very strange because it was working just fine until a few days ago.


Useful Links with Similar Problem
Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...