From: "Gabor Z. Papp" <gzp-2g/1Y3AqmNE@public.gmane.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] mount.nfs command: old glibc missing some flags
Date: Wed, 30 Jul 2008 21:20:02 +0200 [thread overview]
Message-ID: <x6sktrfacd@gzp> (raw)
In-Reply-To: 4890BA36.1060802@RedHat.com
* Steve Dickson <SteveD@redhat.com>:
| > -lblkid doesn't enough in dependency, needs -luuid
| >
| > Is this problem in my e2fsprogs install?
| At least in my world you also need the e2fsprogs-devel package
| installed as well...
libs and headers presents
| > Same apply on glibc 2.3.
| Note that sm-notify is a very short lived process....
| If have found using the -d flag is very handy when starting sm-notify
| by hand... If there is no output, it means the /var/run/sm-notify.pid exists
| which causes sm-notify to immediately exit. So remove that file and try
| again...
Sure done that first. Attached strace output happens on fresh start.
| In general, if there are file(s) in /var/lib/nfs/sm (or /var/lib/nfs/statd/sm
| depending on your distro) means sm-notify did not work. With Fedora, doing
| a 'service nfslock restart' will cause sm-notify to be rerun... I'm not
| sure how to do that with other distros...
Those dirs are empty.
next prev parent reply other threads:[~2008-07-30 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:16 [PATCH] mount.nfs command: old glibc missing some flags Chuck Lever
2008-07-30 6:50 ` Gabor Z. Papp
2008-07-30 18:02 ` Chuck Lever
2008-07-30 19:00 ` Steve Dickson
2008-07-30 19:20 ` Gabor Z. Papp [this message]
2008-07-30 19:48 ` Steve Dickson
2008-07-30 20:37 ` Gabor Z. Papp
2008-07-30 23:18 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2008-07-30 23:58 Chuck Lever
[not found] ` <20080730235637.1447.42422.stgit-lQeC5l55kZ7wdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-07-31 9:28 ` 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=x6sktrfacd@gzp \
--to=gzp-2g/1y3aqmne@public.gmane.org \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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