I can only say that I had a core dump under current on sparc, but the core
file was unusable. Can you compile rcp.lockd with -g in CFLAGS and LDFLAGS
and try to find out with gdb where it aborts?
harti
Hi :)
I investigate a little more this nfs locking issue.
I recompile my system with
I will rpc.lockd with -ggdb as you said and see if it is repeatable.
Unfortunately, I'm not home right now, so I'll do this in 3 o 4 days.
Regards.
Antoine
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
Check to make sure that rpc.statd is running. There was an old bug that
rpc.lockd would dump core if it couldn't find a statd.
Ho, it is running :)
Actually, all my homedir are mounted with NFS, so rpc.lockd get used a lot.
That is why it is an important concern to me.
I couldn't find any
On Sat, 8 Nov 2003, Antoine Jacoutot wrote:
AJHi :)
AJ
AJAre they any know issues with rpc.lockd under -CURRENT.
AJI had a look at the gnats database and did not find anything related.
AJI'm asking this because I have a lot of:
AJkernel: pid 70065 (rpc.lockd), uid 0: exited on signal 11 (core
On Saturday 08 November 2003 12:26, Harti Brandt wrote:
I can only say that I had a core dump under current on sparc, but the core
file was unusable. Can you compile rcp.lockd with -g in CFLAGS and LDFLAGS
and try to find out with gdb where it aborts?
Allright, as soon as I get home in 4/5
On Sat, Nov 08, 2003 at 12:02:03PM +0100, Antoine Jacoutot wrote:
Hi :)
Are they any know issues with rpc.lockd under -CURRENT.
I had a look at the gnats database and did not find anything related.
I'm asking this because I have a lot of:
kernel: pid 70065 (rpc.lockd), uid 0: exited on
On Sat, 8 Nov 2003, Antoine Jacoutot wrote:
Any idea ?
I would be pleased to send more information but I didn't see where to find
more debuging options for rpc.lockd.
Check to make sure that rpc.statd is running. There was an old bug that
rpc.lockd would dump core if it couldn't find a