[systemd-devel] systemd-analyze-197 broken

[Colin Guthrie]

'Twas brillig, and Kok, Auke-jan H at 14/01/13 23:55 did gyre and gimble:
>> > does systemd really need to introduce one 3rd party component
>> > after the next (libmicrohttpd as example) which will sooner
>> > or later terrible break due incompatible changes in this minefiled
> I don't think it's as bad as you portray it, but I have an intern
> software engineer that I will be making systemd-analyze (the non-plot
> parts - the plot parts should be replaced by bootchart IMO) rewrite in
> C, so hopefully we can put some of this behind us soon enough.


I find the systemd-analyze plots pretty useful generally. It would be a
shame to drop it in favour of bootchart if bootchart still requires a
separate init to be run. i.e. "I've got a problem on this boot right
now, I'd like a quick graphical representation of it please!" type use
cases.

I agree in principle with the other posts: i.e. less python deps if
possible (it's just writing an svg? It's just XML why does it need a
whole python backend??) and more useful information about timeouts and
failed jobs etc. etc.

So all I humbly ask here is that plotting from a normal, non-bootcharted
boot is still kept around.

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/