Recent changes to bugs

Wishlist: separate bootchart and bootchartd packages

2013-09-12T07:36:15.042000Z

Dober dan, Ziga and others :-)

As far as I can tell, the specfile in latest SVN only builds one RPM, containing both bootchart and bootchartd.

It would be really good if there were two RPM packages: one containing bootchartd alone, which would not depend on Java etc, and the other containing bootchart, with its heavier Java dependencies.

This would make it much easier to install bootchartd on one machine, and use it to gather boot stats there, then copy the .tgz to another machine with Java installed, and generate the graphs there.

As far as I can tell, in the current source code, there is already a nice clean separation between the information gathering and the graph generation components. So that existing separation just needs to be reflected in the packages.

The Debian project similarly ship just one package 'bootchart', containing both bootchart and bootchartd.

No user control over 'exit' (stop) process names

2013-09-12T07:16:00.885000Z

In latest SVN revision at time of writing, the 'exit' (ie stop-logging) process names are open-coded into the bootlogd shell script. This makes it difficult to do what we want to do - measure time to mount a filesystem (which is mounted from rc.local). The host that will run bootchart doesn't run X, so doesn't have GDM etc installed.

We could work around this by making a shell script named 'gdm-greeter' and running that from rc.local, but I find that really ugly.

A better way would be to add some new variable(s) to the configuration file, allowing user control over the list of exit process name(s).
However, I am not yet sure how to make this play nicely with the script's current behaviour, where it 'knows' that if early login is enabled, it should instead look for mingetty, agetty etc.

I have attached an ugly, untested and incomplete patch to show what I'm thinking.

Bootchart doesn't stop logging in Linux Mint

2013-01-01T17:58:10Z

Bootchart never stops executing when running under Linux Mint. This is because Linux Mint does not use gdm or kdm - it uses mdm

Adding mdm to line 199 of script/bootchartd will fix the issue.

Use /bin/bash instead of /bin/sh

2011-12-21T17:52:00Z

bootchartd complains, if /bin/sh is not really bash. I use dash, and it doesn't work...

Suggest changing interpreter to /bin/bash

Renderer Crash

2009-05-12T08:53:48Z

I am facing a crash of the renderer with the attached data. This was run on an embedded gentoo for ARM.
The bootchartd daemon is known to already have worked on another ARM system.

Parsing bootchart.tgz
Exception in thread "main" java.lang.NumberFormatException: For input string: "CPU"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at org.bootchart.parser.linux.ProcPsParser.parseLog(Unknown Source)
at org.bootchart.Main.render(Unknown Source)
at org.bootchart.Main.main(Unknown Source)

errors in bootchartd

2009-05-03T18:55:49Z

When running "bootchartd init" on Slackware-12.2 (current svn-head, r434) I get the following output:

Starting bootchart logging
/sbin/bootchartd: line 196: local: can only be used in a function
/sbin/bootchartd: line 199: local: can only be used in a function
/sbin/bootchartd: line 201: local: can only be used in a function
/sbin/bootchartd: line 203: [: : integer expression expected

it seems to work fine though.

Big endianess support

2008-11-04T10:09:19Z

bootchart java account Parser does ignore the byte-order flag.

I'm add a dirty hack and will post the patch here.

Perhaps somebody need this.

svg renderer takes forever on long boot times

2008-11-03T16:54:21Z

As in the summary.
When the boot time is very high (e.g. periodic fsck of a partition), the svg renderer takes hours at 100% CPU, and I end up rebooting because I can't kill it even with a sudo kill -9 (PidNum).
Cheers
Marco

Portability fix for mktemp

2008-10-02T20:29:11Z

bootchartd uses:

mktemp -q -t -d bootchart.XXXXXX

which on some systems fails due to the -d being taken as an argument to -t. Using:

mktemp -q -d -t bootchart.XXXXXX

resolves this.

Comments in inittab are not ignored

2007-10-27T16:55:17Z

Problem:
If the bootchartd script detects the default init runlevel from inittab, it does not ignore commented lines (e.g. #id:5:initdefault:).
The coresponding sed line should be changed to ignore commented lines.

Patch attached.

Regards
Sebastian