On Fri, May 05, 2006 at 09:48:02PM -0400, Jeffrey B. Green wrote:
Yes, I like to think of them as co-dependent servers. I'm assuming that
the init levels have something to do with when they are mounted,
therefore: (I'm off to bed now...) -jeff
NFS crossmounts are usually problematic :-) I
On Sat, Dec 03, 2005 at 04:17:56PM -0500, Jeff Green wrote:
Port 2049 seems to have been grabbed by some other package (and am unable to
pin down which it is). See for example:
% netstat -ap | grep 2049
tcp0 0 *:2049 *:* LISTEN
-
On Fri, May 05, 2006 at 08:54:09PM -0400, Jeffrey B. Green wrote:
Yes, in particular, I did a complete reinstall and the problem has not
reappeared. We may have to label this one a mystery.
Well, it isn't really a mystery as such -- the main problem is that portmap
is very fond of assigning
Package: nfs-kernel-server
Version: 1:1.0.7-3
Severity: important
nfs-kernel-server fails on start, e.g.
% invoke-rc.d nfs-kernel-server start
Exporting directories for NFS kernel daemon...done.
Starting NFS kernel daemon: nfsdinvoke-rc.d: initscript nfs-kernel-server,
action start failed.
4 matches
Mail list logo
