From: Christian Reis <kiko@async.com.br>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS@lists.sourceforge.net
Subject: Re: Killing lockd
Date: Thu, 28 Aug 2003 16:30:16 -0300 [thread overview]
Message-ID: <20030828193016.GA1513@async.com.br> (raw)
In-Reply-To: <shslltd4njk.fsf@charged.uio.no>
On Thu, Aug 28, 2003 at 02:58:23PM -0400, Trond Myklebust wrote:
> >>>>> " " == Christian Reis <kiko@async.com.br> writes:
>
> > Is there a way to kill lockd, or to tell it to restart and
> > register again in the portmapper? I do know that something (or
> > maybe it's suicide) tries to wait for lockd to die upon
> > shutting down on our diskless network, without success. Any
> > hints?
>
> Why can't you use pmap_dump + pmap_set? The above type of recovery
> situation is exactly what they have been developed for.
>
> Alternatively, you would have to umount all the partitions that are
> running without 'nolock' set.
Hmmm. This isn't on a client, though, it's on a server - it doesn't
mount any foreign exports. Or did you literally mean partitions?
Now, pmap_dump/_set would have helped *if* I had known about them
previously to killing the portmapper <wink>
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-08-28 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 18:28 Killing lockd Christian Reis
2003-08-28 18:58 ` Trond Myklebust
2003-08-28 19:30 ` Christian Reis [this message]
2003-08-28 19:54 ` Trond Myklebust
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=20030828193016.GA1513@async.com.br \
--to=kiko@async.com.br \
--cc=NFS@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.