os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Revise the information on the rpc.lockd problem some more.

Browse source
This commit is contained in:
Scott Long 2006-04-13 08:18:44 +00:00
parent 0e565d05f3
commit 9dc6b8793f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=27530
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
en/releases/6.1R/todo.sgml
View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.24 2006/04/02 18:58:04 hrs Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.25 2006/04/13 07:47:39 scottl Exp $">
<!ENTITY local.rel "6.1">
<!ENTITY title "FreeBSD 6.1 Open Issues">
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
@ -133,10 +133,10 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
<td>rpc.lockd interoperability problems</td>
<td>&status.unknown;</td>
<td>&a.kuriyama;</td>
<td>After <a href="http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/80389">this commit</a>
rpc.lockd seems to have interoperability problems.
<td>rpc.lockd seems to have interoperability problems that date back a
number of months but have not been reliably identified.
This may be the cause of the many "rpc.lockd no longer interoperates"
bug reports seen on -stable. Unfortunately, rpc.lockd contains a
bug reports seen on -stable. Unfortunately, rpc.lockd also contains a
number of severe architectural issues that make it unsuitable for a
production environment. Fixing these is beyond the scope of the
6.1 release.</td>