All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: "'nfs@lists.sourceforge.net'" <nfs@lists.sourceforge.net>
Subject: Re: rpc.statd  in /sbin or /usr/sbin ??
Date: Mon, 19 Mar 2007 08:52:18 -0400	[thread overview]
Message-ID: <45FE8782.5020001@RedHat.com> (raw)
In-Reply-To: <200703190924.03153.olaf.kirch@oracle.com>



Olaf Kirch wrote:
> On Monday 19 March 2007 02:14, Neil Brown wrote:
>>  The only reason I can see for putting statd in /sbin is if it were
>>  needed for mounting /usr (in cases where /usr is accessed via NFS).
> 
> Can't speak for others, but this is the reason why Suse put it into /sbin too,
> as long as they shipped it.
I can only assuming this was the case as well... Red Hat has
been putting both rpc.lockd and rpc.statd in /sbin
since at least RH 7.1

steved.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-03-19 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19  1:14 rpc.statd in /sbin or /usr/sbin ?? Neil Brown
2007-03-19  8:24 ` Olaf Kirch
2007-03-19 12:52   ` Steve Dickson [this message]
2007-03-22  5:12     ` Neil Brown
2007-03-22 12:10       ` Talpey, Thomas
2007-03-23  3:21         ` Neil Brown

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=45FE8782.5020001@RedHat.com \
    --to=steved@redhat.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 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.