Date: Fri, 06 Dec 2002 11:01:00 -0500 From: "Anthony Volodkin" <anthonyv@brainlink.com> To: freebsd-current@freebsd.org Subject: Re: Status of file locking over NFS Message-ID: <web-17351776@brainlink.com> In-Reply-To: <20021206074428.GA13511@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey, I tried the following. Anyone know what these errors mean? divine# rpc.statd rpc.statd: svc_tp_create: Could not register prog 100024 vers 1 on udp6 rpc.statd: svc_tp_create: Could not register prog 100024 vers 1 on udpr rpc.statd: cannot create udp service divine# rpc.lockd rpc.lockd: unable to register (NLM_PROG, NLM_SM, udp) ---- some useful information ---- divine# uname -a FreeBSD divine.local.non-standard.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Nov 30 04:19:03 GMT 2002 root@divine.local.non-standard.net:/usr/obj/usr/src/sys/DIVINE sparc64 divine# mount 192.168.1.3:/storage3/sparc64-nfsroot on / (nfs) devfs on /dev (devfs, local) /dev/md1 on /var (ufs, local, soft-updates) /dev/md2 on /tmp (ufs, local, soft-updates) divine# ps -aux USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 12 91.8 0.0 0 40 ?? RL 1Jan70 4936:35.05 (idle: cpu0) root 11 90.8 0.0 0 40 ?? RL 1Jan70 4922:31.58 (idle: cpu1) root 1 0.0 0.1 800 392 ?? ILs 1Jan70 0:00.86 /sbin/init -- root 13 0.0 0.0 0 40 ?? WL 1Jan70 0:30.48 (swi1: net) root 14 0.0 0.0 0 40 ?? WL 1Jan70 30:43.88 (swi6: clock) root 2 0.0 0.0 0 40 ?? DL 1Jan70 4:42.81 (g_event) root 3 0.0 0.0 0 40 ?? DL 1Jan70 1:47.53 (g_up) root 4 0.0 0.0 0 40 ?? DL 1Jan70 1:49.32 (g_down) root 16 0.0 0.0 0 40 ?? DL 1Jan70 1:26.15 (random) root 22 0.0 0.0 0 40 ?? WL 1Jan70 0:57.31 (intr2017: hme0) root 5 0.0 0.0 0 40 ?? DL 1Jan70 0:03.56 (pagedaemon) root 6 0.0 0.0 0 40 ?? DL 1Jan70 0:00.00 (vmdaemon) root 7 0.0 0.0 0 40 ?? DL 1Jan70 0:11.40 (pagezero) root 8 0.0 0.0 0 40 ?? DL 1Jan70 0:27.36 (bufdaemon) root 9 0.0 0.0 0 40 ?? DL 1Jan70 0:00.00 (vnlru) root 24 0.1 0.0 0 40 ?? DL 1Jan70 9:54.91 (syncer) root 25 0.0 0.0 0 40 ?? IL 1Jan70 0:01.50 (nfsiod 0) root 26 0.0 0.0 0 40 ?? IL 1Jan70 0:00.43 (nfsiod 1) root 27 0.0 0.0 0 40 ?? IL 1Jan70 0:00.02 (nfsiod 2) root 28 0.0 0.0 0 40 ?? IL 1Jan70 0:00.00 (nfsiod 3) root 83 0.0 0.0 0 40 ?? DL Tue05AM 0:02.99 (md1) root 97 0.0 0.0 0 40 ?? DL Tue05AM 0:00.08 (md2) root 196 0.0 0.2 2504 752 ?? Ss Tue05AM 0:49.69 /usr/sbin/syslogd - root 387 0.0 0.2 3632 1072 ?? Ss Tue05AM 0:17.26 /usr/sbin/cron root 481 0.0 0.2 5760 1112 ?? Is Tue05AM 0:00.05 inetd root 1747 0.0 0.4 13592 2120 ?? Is Tue04PM 0:03.27 sshd root 2011 0.0 0.3 18312 1448 ofw Is Tue05PM 0:00.77 login -p root root 11486 0.0 0.3 1680 1336 ofw S 3:33PM 0:02.21 -csh (csh) root 0 0.0 0.0 0 40 ?? DLs 1Jan70 0:02.04 (swapper) root 11526 0.0 0.1 736 328 ofw R+ 3:44PM 0:00.01 ps -aux root 10 0.0 0.0 0 40 ?? DL 1Jan70 0:00.00 (ktrace) On Thu, 5 Dec 2002 23:44:28 -0800 Kris Kennaway <kris@obsecurity.org> wrote: > On Thu, Dec 05, 2002 at 11:59:31PM -0500, Anthony > Volodkin wrote: > > > According to release notes for 4.7, server-side NFS > locking is supposed > > to be functional. 5.0-DP2's release notes say that > client-side as well > > as server-side locking is functional. So in theory, I > should not be > > having the above issues. > > You need to run rpc.lockd on both sides. > > Kris -- Anthony Volodkin http://non-standard.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?web-17351776>