Bug#411654: bootchartd only works if /bin/sh is bash

2007-05-13 Thread Jörg Sommer
Hello Ziga, hello Guus, Ziga Mahkovec schrieb am Sat 12. May, 21:41 (+0200): On Thu, 2007-05-10 at 11:10 +0200, Jörg Sommer wrote: Do you plan a new release with this patch? I was hoping someone would test the change with dash first. I couldn't reproduce this bug. Maybe the submitter of

Bug#411654: bootchartd only works if /bin/sh is bash

2007-05-13 Thread Guus Sliepen
On Sun, May 13, 2007 at 01:32:20PM +0200, Jörg Sommer wrote: Ziga Mahkovec schrieb am Sat 12. May, 21:41 (+0200): On Thu, 2007-05-10 at 11:10 +0200, Jörg Sommer wrote: Do you plan a new release with this patch? I was hoping someone would test the change with dash first. I couldn't

Bug#411654: bootchartd only works if /bin/sh is bash

2007-05-12 Thread Ziga Mahkovec
On Thu, 2007-05-10 at 11:10 +0200, Jörg Sommer wrote: Do you plan a new release with this patch? I was hoping someone would test the change with dash first. The patch is now in Subversion. Is svn.sf.net down? Probably just a temporary issue with SourceForge, should work fine now. -- Ziga

Bug#411654: bootchartd only works if /bin/sh is bash

2007-05-10 Thread Jörg Sommer
Hello Ziga, Ziga Mahkovec schrieb am Mon 07. May, 18:32 (+0200): On Sat, 2007-05-05 at 13:57 +0200, Jörg Sommer wrote: Yes, if you _use_ an initrd. What about mounting the proc filesystem in bootchartd? I've checked Debian's init scripts and they are aware of a mounted procfs—at least,

Bug#411654: bootchartd only works if /bin/sh is bash

2007-05-07 Thread Ziga Mahkovec
On Sat, 2007-05-05 at 13:57 +0200, Jörg Sommer wrote: Ziga Mahkovec schrieb am Wed 18. Apr, 13:23 (+0200): I don't expect this to be problem. I've tested bootchartd with an unmounted /proc and the log_output functions would simply not log anything. As soon as /proc becomes available, the

Bug#411654: bootchartd only works if /bin/sh is bash

2007-05-05 Thread Jörg Sommer
Hello Ziga, sorry for the late reply. Ziga Mahkovec schrieb am Wed 18. Apr, 13:23 (+0200): On Wed, 2007-04-18 at 11:23 +0200, Jörg Sommer wrote: Ziga Mahkovec schrieb am Sun 15. Apr, 02:30 (+0200): How about we avoid the udev problem (missing /dev/null) by starting the loggers before

Bug#411654: bootchartd only works if /bin/sh is bash

2007-04-18 Thread Jörg Sommer
Hi Ziga, Ziga Mahkovec schrieb am Sun 15. Apr, 02:30 (+0200): On Fri, 2007-03-30 at 02:15 +0200, Jörg Sommer wrote: [...] For job control bootchart needs a heavy rewrite, but I also think it can gain something. The other way is to try to redirect the shell error to /dev/null. What

Bug#411654: bootchartd only works if /bin/sh is bash

2007-04-18 Thread Ziga Mahkovec
On Wed, 2007-04-18 at 11:23 +0200, Jörg Sommer wrote: Ziga Mahkovec schrieb am Sun 15. Apr, 02:30 (+0200): How about we avoid the udev problem (missing /dev/null) by starting the loggers before udev is started? Yes, this might be another way to go. But didn't we get errors because the not

Bug#411654: bootchartd only works if /bin/sh is bash

2007-04-14 Thread Ziga Mahkovec
On Fri, 2007-03-30 at 02:15 +0200, Jörg Sommer wrote: Hello Guus, hello Ziga Hi Jörg (and sorry for the late reply), [...] And there you see, dash tries to open /dev/null. The corresponding code is the following: (dash-0.5.3/src/jobs.c) Thanks for getting to the bottom of this! [...] For

Bug#411654: bootchartd only works if /bin/sh is bash

2007-03-29 Thread Jörg Sommer
Hello Guus, hello Ziga I found the problem. Guus Sliepen schrieb am Tue 27. Mar, 12:46 (+0200): On Thu, Mar 22, 2007 at 05:23:36PM +0100, Jörg Sommer wrote: The patch didn't work. I then reinstalled the original script, but removed all redirections to /dev/null. It still complains about

Bug#411654: bootchartd only works if /bin/sh is bash

2007-03-27 Thread Guus Sliepen
On Thu, Mar 22, 2007 at 05:23:36PM +0100, Jörg Sommer wrote: The patch didn't work. I then reinstalled the original script, but removed all redirections to /dev/null. It still complains about not being able to open /dev/null. Oh, can you add a set -x before the PATH assignment and than

Bug#411654: bootchartd only works if /bin/sh is bash

2007-03-22 Thread Jörg Sommer
Hallo Guus, Guus Sliepen schrieb am Wed 21. Mar, 10:59 (+0100): On Mon, Mar 19, 2007 at 02:16:37PM +0100, Jörg Sommer wrote: Hallo Guus, Jörg Sommer schrieb am Sat 24. Feb, 12:29 (+0100): Guus Sliepen schrieb am Tue 20. Feb, 15:40 (+0100): After booting a few times I noticed that

Bug#411654: bootchartd only works if /bin/sh is bash

2007-03-21 Thread Guus Sliepen
On Mon, Mar 19, 2007 at 02:16:37PM +0100, Jörg Sommer wrote: Hallo Guus, Jörg Sommer schrieb am Sat 24. Feb, 12:29 (+0100): Guus Sliepen schrieb am Tue 20. Feb, 15:40 (+0100): After booting a few times I noticed that it sometimes works OK, but most of the time it doesn't. I guess it's

Bug#411654: bootchartd only works if /bin/sh is bash

2007-02-24 Thread Jörg Sommer
Hi Guus, Hi Ziga, Guus Sliepen schrieb am Tue 20. Feb, 15:40 (+0100): After booting a few times I noticed that it sometimes works OK, but most of the time it doesn't. I guess it's caused by udev mounting a tmpfs over /dev, which makes /dev empty for a short interval. Perhaps you should create

Bug#411654: bootchartd only works if /bin/sh is bash

2007-02-20 Thread Guus Sliepen
On Tue, Feb 20, 2007 at 02:05:46PM +0100, Ziga Mahkovec wrote: Not being able to write to /dev/null could imply a timing problem. Could you please try adding the following to /sbin/bootchartd, at the start of the start() function (line 41): while [ ! -w /dev/null ]; do sleep

Bug#411654: bootchartd only works if /bin/sh is bash

2007-02-20 Thread Guus Sliepen
Package: bootchart Version: 0.9-4 Severity: important I just installed bootchartd on a machine where /bin/sh points to dash. When booting, bootchartd claims not to be able to write to /dev/null and does not log anything. At first I thought my static /dev directory was broken, but that was not the

Bug#411654: bootchartd only works if /bin/sh is bash

2007-02-20 Thread Ziga Mahkovec
On Tue, 2007-02-20 at 12:23 +0100, Guus Sliepen wrote: Please apply the same fix to the Debian package, or remove the bashisms from the script. I recently got a similar report[1], but didn't get enough information to get to the bottom of this (and I don't have access to a dash-based system).