I was attempting to run this patch on a 630-120 using 4.1.2. Although it
did solve our rpc.lockd problems, it also caused our system to crash. I
have got around the problem by booting my old kernel, (still using the new
/etc/rpc.lockd) without any problems (so far).
PS, I have experienced no problems on my 4.1.2 sun4c clients.
- I had a report from someone else <firstname.lastname@example.org> who had problems with
this patch on Sun4m and 4.1.2. They have logged this problem with Sun
support and have had no response after a weeks time.
(Adrian, can you pass this summary on to Sun, and keep me posted
- I had a report of this patch being installed on a 4/670 (sun4m) and on
~100 Sun4c clients running 4.1.3, and they have had no problems.
- Someone reported having had problems on an SS2 (Sun4c) running 4.1.1,
that disappeared just before they were going to back out of the patch.
(I hate it when that happens.)
- I had another report of this patch being applied on an IPC (Sun4c)
running 4.1.2. It has not caused his system to hang, but it didn't fix
his problems either.
So I would have to say there is some sort of problem with this patch when
running 4.1.2 on a Sun4m.
It seems fine on 4.1.2 and 4.1.3 Sun4c clients.
It is dubious on 4.1.1 and 4.1.2 Sun4c servers.
Anyone wanting to know the outcome of what sun finds, should probably keep
in touch with <email@example.com>.
Once again, thanks to everyone for their input, and their patience while
I waited for all the replies, and compiled the results.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:24 CDT