public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Collecting bootchart files after boot
Date: Mon, 16 Jul 2007 10:09:24 +0800	[thread overview]
Message-ID: <1184551764.4477.43.camel@localhost> (raw)
In-Reply-To: <20070716004957.GA26687@crowfix.com>

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



  reply	other threads:[~2007-07-16  2:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16  0:49 [gentoo-user] Collecting bootchart files after boot felix
2007-07-16  2:09 ` W.Kenworthy [this message]
2007-07-16  5:34   ` felix
2007-07-16  8:21 ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1184551764.4477.43.camel@localhost \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox