From: Steve Dickson <SteveD@redhat.com>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: statd simplified
Date: Tue, 03 Feb 2004 10:47:30 -0500 [thread overview]
Message-ID: <401FC292.9030303@RedHat.com> (raw)
In-Reply-To: <20040203101733.GB26315@suse.de>
Hello,
Olaf Kirch wrote:
>On Mon, Feb 02, 2004 at 12:56:59PM -0500, Steve Dickson wrote:
>
>
>>Letting /var/lib/nfs/sm grow uncontrollably (i.e. not using SM_UNMON to
>>clean it up) may not be a good idea... Since users can't go in and clean
>>in up by hand
>>(since they could be removing live state), there probably should be some
>>way to cleaned up (and up to date)
>>
>>
>
>Okay, I could add that. Calling unlink from kernel space is a bit of
>a nuisance, but I'll try :)
>
>
Maybe the user level daemon could be used to do this....
When an SM_UNMON comes in, the kernel could clean up its
state and then forward the message to the daemon that would
cause the file to be removed...
SteveD.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-02-03 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 14:08 statd simplified Olaf Kirch
2004-02-02 17:56 ` Steve Dickson
2004-02-03 10:17 ` Olaf Kirch
2004-02-03 15:47 ` Steve Dickson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 20:06 Peter Astrand
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=401FC292.9030303@RedHat.com \
--to=steved@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.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