All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Barazer <gabriel@oxeva.fr>
To: nfs@lists.sourceforge.net
Subject: bug : sm-notify path is hardcoded into statd
Date: Mon, 23 Jul 2007 18:15:28 +0200	[thread overview]
Message-ID: <46A4D420.1040801@oxeva.fr> (raw)

Hi,

Just found another which happens when nfs utilities are not installed in 
/usr/sbin (e.g. because it's installed in /sbin for a diskless setup), 
statd can't properly call sm-notify because the path to sm-notify is 
hardcoded at utils/statd/statd.c:226 (nfs-utils-1.1.0). To preserve 
consistency with configure switch, we must instead replace it with the 
sbindir variable. (I can't reliably do a patch because I don't know 
enough how to deal with the autotools).

Thanks,

Gabriel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-07-23 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 16:15 Gabriel Barazer [this message]
2007-07-23 20:27 ` bug : sm-notify path is hardcoded into statd Steinar H. Gunderson

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=46A4D420.1040801@oxeva.fr \
    --to=gabriel@oxeva.fr \
    --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.