Re: lockd trouble

Jussi Hamalainen (count@theblah.org)
Tue, 10 Apr 2001 23:01:41 +0300 (EEST)


On Tue, 10 Apr 2001, Jussi Hamalainen wrote:

> program vers proto port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100021 1 udp 1024 nlockmgr
> 100021 3 udp 1024 nlockmgr
> 100005 1 udp 686 mountd
> 100005 2 udp 686 mountd
> 100005 1 tcp 689 mountd
> 100005 2 tcp 689 mountd
> 100003 2 udp 2049 nfs
> 100003 2 tcp 2049 nfs

Duhh. Obviously I should have read the documentation before bashing
my head against the wall. I wasn't running statd. Got it working now,
sorry about that.

I do have a question about lockd. How do I get it back if I need
to restart portmap? Running rpc.lockd doesn't seem to have any
effect whatsoever on the listed rpc services and I can't just
reload the module since nfs depends on it.

-- 
-=[ Count Zero / TBH - Jussi Hämäläinen - email count@theblah.org ]=-

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/