Hmmm. Thanks for the reply. As I say the dbus is a mystery to me. Complete.
In previous versions of fedora I ran the identical posix_spawn code without dbus-daemons being launched, at least not visibly in the gnome-system-monitor. The dbus daemons only appeared somewhere around fedora 22 or fedora 23. They weren't there in earlier fedora releases, eg 15.
I don't understand why a call to posix_spawn launches a dbus session. I certainly didn't request it. The apps I build use QT, and they all talk to each other via TCP/IP . QTWebKit is also linked.
The apps have read/write/execute access to the disk, and the TCP/IP interfaces open and close on each message. I don't do any fancy file sharing between parent and child processes. The launched apps operate independently of the parent.
What might cause a new identity for the connection to be generated ?
Could it be in the environment variables? I pass these environmental variables to posix_spawn:
My understanding is that all my apps should be using the dbus attached to my gnome user session, and, not launching new ones at all.