* [gentoo-user] Collecting bootchart files after boot
@ 2007-07-16 0:49 felix
2007-07-16 2:09 ` W.Kenworthy
2007-07-16 8:21 ` Neil Bothwick
0 siblings, 2 replies; 4+ messages in thread
From: felix @ 2007-07-16 0:49 UTC (permalink / raw
To: gentoo-user
I have been collecting bootchart info for each boot, curiousity and no
more. It is interesting sometimes to look at them and see if minor
tweaks can change things, but I have no serious use for the data.
Thus it took me a while to realize that the .png and .tgz files are
not generated until rc has finished the boot, which is after
local.start has run. I have code in local.start to save the current
bootchart.* files in a time-stamped dir for each boot, and they are
all off by one. It is more amusing than alarming.
I understand why this happens. Is there any way to automatically run
a script like local.start but after rc finishes? I had thought of
putting something in local.stop to copy the current bootchart.* files,
but that smells a bit too kludgery.
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Collecting bootchart files after boot
2007-07-16 0:49 [gentoo-user] Collecting bootchart files after boot felix
@ 2007-07-16 2:09 ` W.Kenworthy
2007-07-16 5:34 ` felix
2007-07-16 8:21 ` Neil Bothwick
1 sibling, 1 reply; 4+ messages in thread
From: W.Kenworthy @ 2007-07-16 2:09 UTC (permalink / raw
To: gentoo-user
untried:
create another init.d script with an "after local.start" parameter - I
think this works
use a batch file to do the saving which includes a sleep command, then
trigger it from local.start using nohup - this has worked for me in the
past.
Billk
On Sun, 2007-07-15 at 17:49 -0700, felix@crowfix.com wrote:
> I have been collecting bootchart info for each boot, curiousity and no
> more. It is interesting sometimes to look at them and see if minor
> tweaks can change things, but I have no serious use for the data.
> Thus it took me a while to realize that the .png and .tgz files are
> not generated until rc has finished the boot, which is after
> local.start has run. I have code in local.start to save the current
> bootchart.* files in a time-stamped dir for each boot, and they are
> all off by one. It is more amusing than alarming.
>
> I understand why this happens. Is there any way to automatically run
> a script like local.start but after rc finishes? I had thought of
> putting something in local.stop to copy the current bootchart.* files,
> but that smells a bit too kludgery.
>
> --
> ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
> Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
> GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
> I've found a solution to Fermat's Last Theorem but I see I've run out of room o
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Collecting bootchart files after boot
2007-07-16 2:09 ` W.Kenworthy
@ 2007-07-16 5:34 ` felix
0 siblings, 0 replies; 4+ messages in thread
From: felix @ 2007-07-16 5:34 UTC (permalink / raw
To: gentoo-user
On Mon, Jul 16, 2007 at 10:09:24AM +0800, W.Kenworthy wrote:
> untried:
>
> create another init.d script with an "after local.start" parameter - I
> think this works
Didn't try it because init.d/local says "after *" and that might lead
to some kind of infinite loop or at least confusion.
> use a batch file to do the saving which includes a sleep command, then
> trigger it from local.start using nohup - this has worked for me in the
> past.
This does, but a 20 second sleep wasn't enough and it only copied part
of the .png which was apparently being generated as my script ran.
It does work, and I will leave it that way with a longer sleep, but I
hope there's a better way :-)
Thanks
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-user] Collecting bootchart files after boot
2007-07-16 0:49 [gentoo-user] Collecting bootchart files after boot felix
2007-07-16 2:09 ` W.Kenworthy
@ 2007-07-16 8:21 ` Neil Bothwick
1 sibling, 0 replies; 4+ messages in thread
From: Neil Bothwick @ 2007-07-16 8:21 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
On Sun, 15 Jul 2007 17:49:57 -0700, felix@crowfix.com wrote:
> I understand why this happens. Is there any way to automatically run
> a script like local.start but after rc finishes? I had thought of
> putting something in local.stop to copy the current bootchart.* files,
> but that smells a bit too kludgery.
Unless you're in the habit of crashing the system, and not running
local.stop, this should work fine. Alternatively, run it from your
desktop if this is possible. Put in in your main user's .xinirc or, if
you use KDE, in ~/.kde/Autostart.
--
Neil Bothwick
If all the world is a stage, where is the audience sitting?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-07-16 8:27 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-16 0:49 [gentoo-user] Collecting bootchart files after boot felix
2007-07-16 2:09 ` W.Kenworthy
2007-07-16 5:34 ` felix
2007-07-16 8:21 ` Neil Bothwick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox