Hi, The tool 'qlop' from the portage-utils doesn't show up the current merge because recent sandbox ebuilds does not use /tmp/sandboxpids.tmp anymore. Also 'genlop' was affected by this problem. See http://bugs.gentoo.org/show_bug.cgi?id=99823 Please fix that. Regards Ruben Reproducible: Always Steps to Reproduce: 1.emerge something 2.run 'qlop -c' Actual Results: 'lop: Could not open pidfile '/tmp/sandboxpids.tmp': No such file or directory' Expected Results: The current running merge process should show up including time information.
yeah i just havent gotten around to rewriting qlop
portage-utils-0.1.3: -F, --pidfile <arg> * Read emerge pidfile instead of /tmp/sandboxpids.tmp
What do you set as '<arg>' - where do I find that "emerge pidfile"? Please give me some information about that. Regards Ruben
A while ago there was a security problem with the handling of this pid file your after. that was bug #96782 After that bug was fixed it invalidated the entire sandbox pids idea as it uses a random tmpfile for pids handling. What the genlop code does now is an execve() is /bin/ps now (but that is not a very good idea either) I assume what SpanKY wants todo at some point is parse the /proc/[0-9]*/* file system or dump the option all together.
Created attachment 70884 [details, diff] Patch for SpanKY Not the finished polished double-checked stuff, but basically works for me.
thanks, should be fixed in cvs now
SpankY: nice work. Love the #else errf() handler when __QLOP_CURRENT__ is not defined.
