Re: problem with 114 sched.* changes (not the gcc one)
Linus Torvalds (torvalds@transmeta.com)
Mon, 10 Aug 1998 16:01:36 -0700 (PDT)
On Mon, 10 Aug 1998, Ion Badulescu wrote:
>
> Attaching strace to amd after it hangs is a waste of time.. while starting
> amd under strace reveals little new. amd forks the user-space NFS server,
> then forks a child which acts as mount, contacts the server as an
> NFS server, gets a file handle and calls mount(2). The first call fails
> with ENOSYS, the second one hangs, as do any following mounts -- amd
> forks a mount-child for each mount point it manages.
Let me check one more thing - is this with KMOD enabled, and "nfsd" as a
kernel module? Does it also happen if nfsd is compiled into the kernel?
The ENOSYS makes me wonder. I don't see that you should ever get ENOSYS
under normal circumstances..
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html