All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Reis <kiko@async.com.br>
To: NFS@lists.sourceforge.net
Subject: Killing lockd
Date: Thu, 28 Aug 2003 15:28:08 -0300	[thread overview]
Message-ID: <20030828182808.GC1166@async.com.br> (raw)


So today I had to restart my portmapper (bizarre fact of life) and after
restarting it and all the services running, I noticed that locking was
broken. The reason was that clients no longer could contact the lockd,
since it wasn't registered after we reran the portmapper.

Now that would be fixable if we could tell lockd to restart, or kill it
and restart it manually, but I don't know how to do it. I had to reboot
the server.

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?

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

             reply	other threads:[~2003-08-28 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 18:28 Christian Reis [this message]
2003-08-28 18:58 ` Killing lockd Trond Myklebust
2003-08-28 19:30   ` Christian Reis
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=20030828182808.GC1166@async.com.br \
    --to=kiko@async.com.br \
    --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.