top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

systemd service spawning packagekit daemon

+1 vote

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 LinkedIn Share Button

1 Answer

+1 vote

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

answer Aug 29, 2013 by Ahmed Patel
Similar Questions
0 votes

I want to start a systemd service (dhcpd) , but only if a link to the internet is present. I don't want the service to start on boot.

systemctl start doesn't work unless the service is enabled.

This works, but it's very kludgy:

 systemctl enable 
 systemctl start 
 systemctl disable 

Any better ideas ?

+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/ not readable (yet?)
after start: No such file or directory".

I've checked, and is in place:

$ sudo cat /run/ 
/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.

0 votes

I completed my installation of solid-state drives and, of course, a new installation of F27.

And now: what happened to my system configuration tools? How do I start and stop services?

My biggest problem is Samba. I can't see any Windows computers on my network, and they can't see me. (I can, however, see a network printer. That, I configured in the System Settings app.)