Seth Vidal <skvidal@xxxxxxxxxxxxxxxxx> writes: > Last week doing some noodling around I wrote up a couple of new > yum-utils but I'd like some constructive feedback on them. > > first: > - shows what running programs should be restarted due to updates being > applied. > > http://skvidal.wordpress.com/2009/11/03/what-needs-to-be-restarted/ This isn't terrible, but it needs a few tweaks before we put it in, IMO: 1. Tell people not running as root they will get wrong data. 2. Should check more than just smaps, one obvious problem is that python apps. only come up as python (probably the only thing to do is parse cmdline, and then check the first arg. to python). 3. Another big problem is to do with shared libraries, atm. I have: james 3028 0.0 0.0 132156 3100 ? S Sep15 0:00 kerneloops-appl /proc/3028/smaps:... 112903 /usr/lib64/libgtk-x11-2.0.so.0.1600.5 (deleted) ...which doesn't exist. The file /usr/lib64/libgtk-x11-2.0.so.0.1600.6 does exist, and was installed on the 8th of Nov. The "obvious" solution here is that anything with a (deleted) suffix automatically means it needs to be restarted. Of course there are also a bunch of things like: /proc/3028/smaps:... 112902 /usr/lib64/libatk-1.0.so.0.2511.1.#prelink#.egtvwq (deleted) ...which people may/may-not appreciate getting warnings about. 4. Might be nice to integrate history in the output. 5. Might be nice to have a "yum.proc" which contains some of this and the locking stuff. Feel free to ignore #4 and #5 though. > second: > a command-line pipes/parsing "friendly" yum-util. > http://skvidal.wordpress.com/2009/11/06/playing-with-another-yum-util/ This one makes me twitch. -- James Antill -- james@xxxxxxx _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
