How to find the monitor pid
matthiasclasen opened this issue · 4 comments
man xdg-app-enter says:
MONITORPID must be the monitor pid of a running sandbox. How do I find that ? I can imagine a future in which gnome-system-monitor knows enough about xdg-app to show this kind of information for running apps.
In the meantime, maybe a --show-monitor-pid option would be nice. Could also make the logging options more extendible:
--log=system-bus
--log=session-bus
--log=monitor-pid
Its the ps line that looks like:
alex 27903 0.1 0.0 6640 904 pts/0 S 08:50 0:00
xdg-app-helper org.gnome.gedit launcher
We don't really keep track of the running sandboxes in a centralized
fashion, so its hard to list them. Maybe we can hang that info off the
systemd --user slice though. I think you can add extra data there.
On Sat, Apr 16, 2016 at 5:15 PM, matthiasclasen notifications@github.com
wrote:
man xdg-app-enter says:
MONITORPID must be the monitor pid of a running sandbox. How do I find
that ? I can imagine a future in which gnome-system-monitor knows enough
about xdg-app to show this kind of information for running apps.In the meantime, maybe a --show-monitor-pid option would be nice. Could
also make the logging options more extendible:--log=system-bus
--log=session-bus
--log=monitor-pid—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#133
Looks like this sortof works to poke the pid out of the service name:
ls /sys/fs/cgroup/systemd/user.slice/user-$(id -u).slice/user@$(id -u).service/ | grep Terminix | sed -e s/.scope$// -e s/.*-//
Unfortunately we don't know the monitor pid at the time we create the slice. Otherwise we could possibly as systemd to store that data for us.
This issue was moved to flatpak/flatpak#14