public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
	Sven Ladegast <sven@linux4geeks.de>,
	linux-kernel@vger.kernel.org
Subject: Re: KLive: Linux Kernel Live Usage Monitor
Date: Tue, 30 Aug 2005 18:16:34 +0200	[thread overview]
Message-ID: <20050830161634.GR8515@g5.random> (raw)
In-Reply-To: <1125419618.8276.30.camel@localhost.localdomain>

On Tue, Aug 30, 2005 at 05:33:38PM +0100, Alan Cox wrote:
> Just follow the LSB specification and about the only thing thats totally
> out of field is Slackware.

Fair enough, though one line like '(sleep 60; twistd ...) & in
/etc/init.d/boot.local would have been a bit simpler for a quick and
dirty autoinstall .sh script (that's the simplest way I install it in my system).

> Right thats my first reaction, 6Mbytes of unauditable weirdness versus a

;)

> tiny C program or a shell script using netcat.
> 
> echo "Reporting boot: "
> (echo "BOOT:"$(cat /etc/lum-serial)":"$(uname -a)"::") | nc -u -w 10
> testhost.example.com 7658

Client completely stateless couldn't get right suspend to disk as far as
I can tell.

Tiny C program will be less tiny than the current tac file and the
package would immediately become arch dependent. Plus if you want to run
it as user nobody the twistd -u/g --pidfile --logfile and all the rest
in twisted make life so much easier. On my systems I've other services
running in background with twistd so perhaps I'm biased because I share
almost all of it ;).

> For one distro perhaps. Using a proper init service script makes it work
> for pretty much everyone. 

I'm not very optimistic about the depdency chain to be distro
indipendent, but I will look into that shortly and I guess here I'm
running a bit offtopic.

Thanks!

  reply	other threads:[~2005-08-30 16:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  3:09 KLive: Linux Kernel Live Usage Monitor Andrea Arcangeli
2005-08-30  8:01 ` Sven Ladegast
2005-08-30  8:29   ` Rogier Wolff
2005-08-30  8:53     ` Sven Ladegast
2005-08-30  9:40       ` Rogier Wolff
2005-08-30  9:54         ` Bernd Petrovitsch
2005-08-30 15:10         ` Andrea Arcangeli
2005-08-30 16:33           ` Alan Cox
2005-08-30 16:16             ` Andrea Arcangeli [this message]
2005-08-30 16:56               ` Alan Cox
2005-08-30 16:40                 ` Andrea Arcangeli
2005-08-31 18:32               ` Pavel Machek
2005-09-01 15:19                 ` Andrea Arcangeli
2005-08-30 16:36             ` Jesper Juhl
2005-08-30 22:11         ` Bill Davidsen
2005-08-31  1:49           ` Andrea Arcangeli
2005-08-31 19:14             ` tony.luck
2005-08-31 19:47               ` Andrea Arcangeli
2005-09-05 18:26                 ` Andrea Arcangeli
2005-08-30 14:45     ` Andrea Arcangeli
2005-08-30 14:36   ` Alan Cox
2005-08-30 22:43     ` Sven Ladegast
2005-08-30 23:25       ` Alan Cox
2005-08-30 23:19         ` Sven Ladegast
2005-08-31 13:34           ` Alan Cox
2005-08-31 14:28             ` Sven Ladegast
2005-08-31 21:23               ` Andrea Arcangeli
2005-08-30 14:56   ` Andrea Arcangeli
2005-08-31 18:20     ` Pavel Machek
2005-09-01 15:23       ` Andrea Arcangeli
2005-09-01 12:26     ` Sven Ladegast
2005-09-05 22:05 ` Marc Giger
2005-09-05 23:13   ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2005-08-30 17:08 Wilkerson, Bryan P
2005-08-30 17:44 ` linux-os (Dick Johnson)
2005-08-30 20:31 ` Andrea Arcangeli

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=20050830161634.GR8515@g5.random \
    --to=andrea@suse.de \
    --cc=R.E.Wolff@BitWizard.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sven@linux4geeks.de \
    /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