Re: Switching to kernel nfs (was: mutt and an nfs mounted home directory)

2001-08-23 Thread Jason Majors
And the winner of this year's Dumbass award is...ME. I was testing the mountability (is that a word?) of the nfs served directories on my firewall, because I turn the workstation off when I'm not using it (like now when I'm at "work"). The firewall doesn't have nfs-common installed. I tested it mou

Re: Switching to kernel nfs (was: mutt and an nfs mounted home directory)

2001-08-23 Thread Michael Heldebrant
On 23 Aug 2001 15:59:04 -0700, Jason Majors wrote: > On Thu, Aug 23, 2001 at 04:48:14PM -0500, Dave Sherohman scribbled... > > Try reinstalling nfs-kernel-server, portmapper, and all of their > > dependencies. I was getting the same sort of problems a little while > > back with both nfs and nis

Re: Switching to kernel nfs (was: mutt and an nfs mounted home directory)

2001-08-23 Thread Jason Majors
On Thu, Aug 23, 2001 at 04:48:14PM -0500, Dave Sherohman scribbled... > Try reinstalling nfs-kernel-server, portmapper, and all of their > dependencies. I was getting the same sort of problems a little while > back with both nfs and nis and that's what solved them. Apparently, > there was some

Re: Switching to kernel nfs (was: mutt and an nfs mounted home directory)

2001-08-23 Thread Dave Sherohman
On Thu, Aug 23, 2001 at 12:47:25PM -0700, Jason Majors wrote: > When I remove the no_root_squash option, it says it starts, but I get > mount: RPC: Unable to receive; errno = Connection refused > on the client and /var/lib/nfs/xtab is empty. > What do I have to do to get the kernel server to run?

Re: Switching to kernel nfs (was: mutt and an nfs mounted home directory)

2001-08-23 Thread Jason Majors
I have the kernel server up, but now it won't export my directories. I have lines like: /usr/local/oggs 192.168.1.2(ro) 192.168.1.4(ro) 192.168.1.1(ro) /home 192.168.1.2(rw, no_root_squash) 192.168.1.4(rw) in my /etc/exports file. When I (re)start nfs-kernel-server I get: Exporting di

Re: Switching to kernel nfs (was: mutt and an nfs mounted home directory)

2001-08-23 Thread Dave Sherohman
On Thu, Aug 23, 2001 at 10:23:31AM -0700, Jason Majors wrote: > I have the packages nfs-common, nfs-kernel-server, and nfs-server. How'd you manage that? nfs-kernel-server and nfs-server conflict. > I have nfs compiled into my kernel. Assuming you have NFS server support in your kernel, you sho

Switching to kernel nfs (was: mutt and an nfs mounted home directory)

2001-08-23 Thread Jason Majors
On Thu, Aug 23, 2001 at 09:17:31AM -0500, Dave Sherohman scribbled... > On Wed, Aug 22, 2001 at 09:36:35PM -0700, Jason Majors wrote: > 1) Use knfsd instead of nfsd on the nfs server. Quick and easy > (although it does require a kernel reconfigure/rebuild unless you > already have nfs server s

Re: mutt and an nfs mounted home directory

2001-08-23 Thread Dave Sherohman
On Wed, Aug 22, 2001 at 09:36:35PM -0700, Jason Majors wrote: > I have an nfs mounted home directory where the user and group ids match. > I can write in the ~/.mutt directory and even edit my inbox and sentbox on the > client, but when I run mutt on the client machine, it tells me that the > mail

Re: mutt and an nfs mounted home directory

2001-08-23 Thread David Roundy
On Thu, Aug 23, 2001 at 07:29:48AM +0200, Leonardo Macchia wrote: > On Wed, Aug 22, 2001 at 21:36:35 -0700, Jason Majors wrote: > > > but when I run mutt on the client machine, it tells me that the > > mailbox is read only. > > Maybe it's a problem of file locking: mutt try to lock the mailbox bu

Re: mutt and an nfs mounted home directory

2001-08-23 Thread Leonardo Macchia
On Wed, Aug 22, 2001 at 21:36:35 -0700, Jason Majors wrote: > but when I run mutt on the client machine, it tells me that the > mailbox is read only. Maybe it's a problem of file locking: mutt try to lock the mailbox but does the server support file locking? Do you use knfsd (nfs-kernel-server) o

mutt and an nfs mounted home directory

2001-08-22 Thread Jason Majors
I have an nfs mounted home directory where the user and group ids match. I can write in the ~/.mutt directory and even edit my inbox and sentbox on the client, but when I run mutt on the client machine, it tells me that the mailbox is read only. Is there a setting in mutt I can change to make it us