Whoops, this was meant to go to a wider audience, not just to Stan...
(Lukas, this is that email I mentioned earlier re packaging).
----- Forwarded Message -----
From: "Nathan Scott" <nathans@xxxxxxxxxx>
To: "Stan Cox" <scox@xxxxxxxxxx>
Sent: Tuesday, 24 March, 2015 10:42:20 AM
Subject: [RFC] possible pcp atop rework
Hi Stan,
I've been looking into extending pmatop to allow top container resources
to be displayed, and wonder if its worthwhile stepping back and rethinking
our strategy with atop before starting any surgery.
Awhile back we chatted about whether having a custom atop was ideal - and
we discussed the possibility of basing the pcp tool on the upstream source
from www.atoptool.nl (gpl, C code). At the time the issue was around all
the window resizing problems we had, but there are other issues too. From
a look through the site and code, I see there are many, many features we
are missing from the upstream tool (incl. config files, color, many other
display modes). These all look like genuinely useful features, and would
involve significant effort to do ourselves.
So, just wanted to checkin with you mainly - do you have any thoughts as to
whether we should / shouldn't attempt a switch (essentially replacing the
existing implementation with upstream + tweaks to use the PMAPI)? The code
appears quite clean, and maybe we could even begin to foster a relationship
sharing fixes/features with the original author (have you discussed the pcp
clone with him at all so far?).
Thanks!
--
Nathan
|