Bill Moran writes:
Have you tried contacting the Foundation?
http://www.freebsdfoundation.org/
It's my understanding that they coordinate most of this money -
developers stuff ...
I think I explored that route. It's been a month or so now.. but if memory
serves me well that was not a viable
Kris Kennaway writes:
There are a number of PRs I filed, but those aren't all of the
problems. It will require fairly major work to fix - the best hope
would be if someone was funded to work on it.
A couple of months back the place I work for had a number of issues with
NFS. We tried to
In response to Francisco Reyes [EMAIL PROTECTED]:
Kris Kennaway writes:
There are a number of PRs I filed, but those aren't all of the
problems. It will require fairly major work to fix - the best hope
would be if someone was funded to work on it.
A couple of months back the place I
Hi,
That's interesting. Are you getting a could not lock the passwd
file: EOPNOTSUPP failure with rpc.lockd not enabled?
Negative, I rebuild the kernel on one box today, commented out
rpc.lockd=YES in /etc/rc.conf and rebooted into single user mode and
remounted / rw.
I then ran
On Thu, Sep 21, 2006 at 04:12:03PM -0700, Perry Hutchison wrote:
File locking works reasonably well within a single system (defined
as a combination of hardware and software that all crashes together
:) I doubt anyone will ever get it to work all that well when the
locks must be shared
Hi,
Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still
able to run adduser and so on ?
Safely? No. But then, flock() doesn't work via NFS even if
rpc.lockd is running, so you aren't any worse off.
flock() .. hmm yeah, I discoverd trouble with sendmail as well, it
On Sep 22, 2006, at 11:02 AM, Robert Joosten wrote:
Hmmm, is there a way to run pxe-boxes without rpc.lockd and then
still
able to run adduser and so on ?
Safely? No. But then, flock() doesn't work via NFS even if
rpc.lockd is running, so you aren't any worse off.
flock() .. hmm yeah, I
Hi,
I observed running a pxe client running fbsd 5.[45] being served by
nfs-box running 5 (and 4
nowadays because of asr0 trouble due to geom) having disabled
rpc.lockd
the box doens't let me run adduser, but with rpc.lockd enabled it's
fine
with 'em. Is that strange or am I missing
I recall that FreeBSD 6.1 had some NFS lockd issues that were a
show stopper at one time for me however I'm having trouble finding
information on the current state of NFS. Anyone have a pointer to
information?
--
Michael Conlen
___
freebsd
On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:
I recall that FreeBSD 6.1 had some NFS lockd issues that were a
show stopper at one time for me however I'm having trouble finding
information on the current state of NFS. Anyone have a pointer to
information?
rpc.lockd
On Sep 21, 2006, at 2:22 PM, Kris Kennaway wrote:
On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:
I recall that FreeBSD 6.1 had some NFS lockd issues that were a
show stopper at one time for me however I'm having trouble finding
information on the current state of NFS. Anyone
On Thu, Sep 21, 2006 at 02:42:44PM -0400, Michael Conlen wrote:
On Sep 21, 2006, at 2:22 PM, Kris Kennaway wrote:
On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:
I recall that FreeBSD 6.1 had some NFS lockd issues that were a
show stopper at one time for me however I'm
On Sep 21, 2006, at 2:45 PM, Kris Kennaway wrote:
On Thu, Sep 21, 2006 at 02:42:44PM -0400, Michael Conlen wrote:
On Sep 21, 2006, at 2:22 PM, Kris Kennaway wrote:
On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:
I recall that FreeBSD 6.1 had some NFS lockd issues
wrote:
I recall that FreeBSD 6.1 had some NFS lockd issues that were a
show stopper at one time for me however I'm having trouble finding
information on the current state of NFS. Anyone have a pointer to
information?
rpc.lockd remains unreliable; avoid using it if practical
On Sep 21, 2006, at 11:42 AM, Michael Conlen wrote:
On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:
I recall that FreeBSD 6.1 had some NFS lockd issues that were a
show stopper at one time for me however I'm having trouble finding
information on the current state of NFS. Anyone
Hi,
rpc.lockd remains unreliable; avoid using it if practical.
Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still
able to run adduser and so on ?
Regards,
Robert
___
freebsd-questions@freebsd.org mailing list
On Thu, Sep 21, 2006 at 11:43:16PM +0200, Robert Joosten wrote:
Hi,
rpc.lockd remains unreliable; avoid using it if practical.
Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still
able to run adduser and so on ?
Use the nolockd option to mount_nfs, that's what I meant
Hi Kris,
rpc.lockd remains unreliable; avoid using it if practical.
Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still
able to run adduser and so on ?
Use the nolockd option to mount_nfs,
nolockd, aha. Okay, I'll look at that, thx.
Regards,
Robert
On Sep 21, 2006, at 2:43 PM, Robert Joosten wrote:
rpc.lockd remains unreliable; avoid using it if practical.
Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still
able to run adduser and so on ?
Safely? No. But then, flock() doesn't work via NFS even if
rpc.lockd is
rpc.lockd remains unreliable; avoid using it if practical.
statd and lockd have been problematic ever since Sun invented them
a couple of decades ago, at least partly because what they are
trying to do is fundamentally not computable. (There is no way to
distinguish between the other side
20 matches
Mail list logo
