You are not logged in.

#1 2016-10-18 19:46:01

FlowIt
Member
Registered: 2014-10-25
Posts: 239

xfconfd started as child of systemd

I logged in into tty2, so graphical environment was started. top -u username showed by that xfconfd was running as a child of systemd. Can somebody explain where I can change this behaviour? xfconfd should only be started when xfce4-session is started. I looked through all systemctl list* outputs but found no hints.

Offline

#2 2016-10-18 20:57:39

ayekat
Member
Registered: 2011-01-17
Posts: 1,590

Re: xfconfd started as child of systemd

Traditionally, the init process (PID 1, in this case systemd) "takes over" processes that have been spawned by processes that no longer exist. So you can't really infer anything from its parent PID.

In the case of xfconfd, it is a dbus service, so if you want to disable that... - well, unfortunately, all I've found is this unanswered thread.


pkgshackscfgblag

Offline

#3 2016-10-18 22:29:22

FlowIt
Member
Registered: 2014-10-25
Posts: 239

Re: xfconfd started as child of systemd

My question was not why systemd is the parent process but rather why xfconfd is started at all (in a non graphical environment). I don't want to disable xfconfd, just prevent it from starting "on its own" (at least it seems that it does) and only be started if xfce4-session is started.

Offline

#4 2016-10-21 13:59:22

ayekat
Member
Registered: 2011-01-17
Posts: 1,590

Re: xfconfd started as child of systemd

Ah, I'm sorry.
Although, it will likely still boil down to the question of how to prevent dbus from starting xfconfd. But I'm unable to help you on the xfce4-session matter, unfortunately.


pkgshackscfgblag

Offline

Board footer

Powered by FluxBB