From: Olaf Kirch <okir@suse.de>
To: Chip Salzenberg <chip@pobox.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Proposal: Starting statd on demand
Date: Tue, 13 Apr 2004 10:59:23 +0200 [thread overview]
Message-ID: <20040413085923.GD15896@suse.de> (raw)
In-Reply-To: <20040409180352.GH2767@perlsupport.com>
On Fri, Apr 09, 2004 at 02:03:52PM -0400, Chip Salzenberg wrote:
> It's a well-known security principle that services should not be running
> when they are not needed.
>
> I would like to make statd follow that principle.
>
> Does anyone have a suggestion on how? I don't want to reinvent an
> already-proposed wheel.
You may want to try my kernel statd patch. It implements a minimal
statd that just supports NULL and SM_NOTIFY in kernel, as an additional
RPC program registered on the same port as lockd.
Note that you still need to have some user land support for statd
which sends out the SM_NOTIFY calls on reboot.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-04-13 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 18:03 Proposal: Starting statd on demand Chip Salzenberg
2004-04-13 8:59 ` Olaf Kirch [this message]
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=20040413085923.GD15896@suse.de \
--to=okir@suse.de \
--cc=chip@pobox.com \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.