Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: mehta kiran <kiranmehta1981@yahoo.com>
Cc: "Aswathanarayana, Chetan (STSD)" <chetan.aswathanarayana@hp.com>,
	nfs@lists.sourceforge.net
Subject: Re: lockd grace period
Date: Mon, 31 Jan 2005 10:01:59 -0500	[thread overview]
Message-ID: <41FE4867.4070709@RedHat.com> (raw)
In-Reply-To: <20050131143610.1250.qmail@web51604.mail.yahoo.com>



mehta kiran wrote:

>Hi , 
>          this means that if  lockd alone is running
>since a long time and if now i start nfsd , 
>
hmm... why would you ever have lockd running "alone"?
Meaning what good is it w/out rpc.nfsd? Also how are
you doing that since one of the first things rpc.nfsd does
is bring up lockd().....

steved.



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-01-31 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 12:50 lockd grace period Aswathanarayana, Chetan (STSD)
2005-01-31 14:36 ` mehta kiran
2005-01-31 15:01   ` Steve Dickson [this message]
2005-01-31 15:09     ` mehta kiran
2005-01-31 16:01       ` Steve Dickson
2005-01-31 14:58 ` Steve Dickson
2005-01-31 15:01   ` mehta kiran
2005-01-31 23:07   ` Dan Stromberg
2005-01-31 23:57     ` Trond Myklebust
2005-02-01  3:07     ` Steve Dickson
  -- strict thread matches above, loose matches on Subject: below --
2005-02-01 10:46 mehta kiran
2005-01-31  7:41 mehta kiran
2005-01-31 12:33 ` Steve Dickson

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=41FE4867.4070709@RedHat.com \
    --to=steved@redhat.com \
    --cc=chetan.aswathanarayana@hp.com \
    --cc=kiranmehta1981@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox