Hi,
On 05/08/2015 09:00 AM, Petter Adsen wrote:
> On Fri, 8 May 2015 00:50:24 -0400
> Gene Heskett wrote:
>> On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote:
>>> On Fri, 8 May 2015 00:03:22 -0400
>>> Gene Heskett wrote:
>>>
>>> i just finished wrestling with NFS set-up problems myself.
>
* Petter Adsen [2015-05-08 13:03 +0200]:
> On Fri, 8 May 2015 06:51:43 -0400
> Gene Heskett wrote:
>
> > On Friday 08 May 2015 02:55:53 Petter Adsen wrote:
> > > That _is_ what you want, isn't it?
> >
> > root does not need write perms, but I do. If it takes root to do
> > something, that is
On Fri, 8 May 2015 06:51:43 -0400
Gene Heskett wrote:
> On Friday 08 May 2015 02:55:53 Petter Adsen wrote:
> > That _is_ what you want, isn't it?
>
> root does not need write perms, but I do. If it takes root to do
> something, that is what the ssh -Y session as me, using sudo is for.
If you
On Friday 08 May 2015 02:55:53 Petter Adsen wrote:
> On Fri, 8 May 2015 00:50:24 -0400
>
> Gene Heskett wrote:
> > On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote:
> > > On Fri, 8 May 2015 00:03:22 -0400
> > >
> > > Gene Heskett wrote:
> > > > Greetings all;
> > > >
> > > >
> > > > Next i
On Fri, 8 May 2015 00:50:24 -0400
Gene Heskett wrote:
>
>
> On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote:
> > On Fri, 8 May 2015 00:03:22 -0400
> >
> > Gene Heskett wrote:
> > > Greetings all;
> > >
> > >
> > > Next is the box on my cnc lathe, #3. But now, not even root can
> > > m
On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote:
> On Fri, 8 May 2015 00:03:22 -0400
>
> Gene Heskett wrote:
> > Greetings all;
> >
> >
> > Next is the box on my cnc lathe, #3. But now, not even root can
> > make a third directory on this /net subdir, No Permissions. And the
> > name o
On Fri, 8 May 2015 00:03:22 -0400
Gene Heskett wrote:
> Greetings all;
>
> Next is the box on my cnc lathe, #3. But now, not even root can make a
> third directory on this /net subdir, No Permissions. And the name of
> the dir could be LanceRumpleStiltSkin & root still can't make the
> dir
On Thu, 23 Apr 2015 23:54:45 -0600
Bob Proulx wrote:
> bri...@aracnet.com wrote:
> > however the client side mount commands are apparently wrong because
> > I get this:
> >
> > mount.nfs4: mounting server:/nfs4exports/home/user1 failed, reason given by
> > server:
> > No such file or director
bri...@aracnet.com wrote:
> however the client side mount commands are apparently wrong because
> I get this:
>
> mount.nfs4: mounting server:/nfs4exports/home/user1 failed, reason given by
> server:
> No such file or directory
>
> and as usual the error message is completely unhelpful because
On Mon, Dec 8, 2008 at 6:57 PM, Brian Schrock <[EMAIL PROTECTED]> wrote:
> I am testing a courier-postfix setup using nfs for the Maildir folders
> on debian etch, and my client machine is debian/lenny. Everything
> seems to work just peachy except for when I use pop/imap for access to
> the mail.
On Tue, Jul 29, 2008 at 06:47:08AM +0200, André Berger wrote:
> * Alex Samad (2008-07-29):
> > On Mon, Jul 28, 2008 at 12:05:58PM +0200, André Berger wrote:
> > > * Alex Samad (2008-07-28):
> > >
> > > > on the nas box
> > > >
> > > > /exports/shared
> > > > -async,no_subtree_check,no_root_squas
* Alex Samad (2008-07-29):
> On Mon, Jul 28, 2008 at 12:05:58PM +0200, André Berger wrote:
> > * Alex Samad (2008-07-28):
> >
> > > on the nas box
> > >
> > > /exports/shared
> > > -async,no_subtree_check,no_root_squash,insecure,mp=/exports/shared
> > > 192.168.8.0/22(rw)
> >
> > Try
> >
> >
On Mon, Jul 28, 2008 at 12:05:58PM +0200, André Berger wrote:
> * Alex Samad (2008-07-28):
>
> > on the nas box
> >
> > /exports/shared
> > -async,no_subtree_check,no_root_squash,insecure,mp=/exports/shared
> > 192.168.8.0/22(rw)
>
> Try
>
> /exports/shared 192.168.8.0/22(rw,async,no_subtree
* Alex Samad (2008-07-28):
> on the nas box
>
> /exports/shared
> -async,no_subtree_check,no_root_squash,insecure,mp=/exports/shared
> 192.168.8.0/22(rw)
Try
/exports/shared 192.168.8.0/22(rw,async,no_subtree_check,no_root_squash)
and "exportfs -rv"
On the Mac, add to /etc/fstab (assuming
At 18:43 20/07/2005, you wrote:
At 22:02 19/07/2005, you wrote:
No, kernel NFS can be either compiled or loaded as a module into a custom
kernel.
Does anyone know which NFS server I *should* be using? Does anyone know
why lockd fails to run?
But the userspace daemons
(/sbin/rpc.lockd an
At 22:02 19/07/2005, you wrote:
No, kernel NFS can be either compiled or loaded as a module into a custom
kernel.
Does anyone know which NFS server I *should* be using? Does anyone know why
lockd fails to run?
But the userspace daemons
(/sbin/rpc.lockd and /sbin/rpc.statd) don't seem to
Stephen Tait wrote:
I've just been rejigging my file server following the upgrade to Sarge and
have finally tried to sort out some niggling problems.
Mainly, lockd doesn't seem to be running - I see the following entries all
the time in my client machines (all gentoo):
nfs warning: mount ver
Hi,
I just remembered something: nfs might not let you export cdroms. I had
this with redhat about a year ago. You also can not proxy nfs (that
is: install a nfs server and mount a nfs mounted filesystem). I do not
know what the status is now.
I do know that the exports file is vary annoying, esp
On Wed, 14 Mar 2001, Forrest English wrote:
> ok, here's what i do on the server.
>
> /etc/exports file contains
> /cdrom 192.168.2.30
>
> and the client's fstab contains
> 192.168.1.10:/cdrom /nfscdrom nfs rsize=1024,wsize=1024 0 0
>
> i on the server, i then did... /etc/init.d/nfs-server
On Wed, Mar 14, 2001 at 10:02:29PM -0800, Forrest English wrote:
> ok, here's what i do on the server.
>
> /etc/exports file contains
> /cdrom 192.168.2.30
>
> and the client's fstab contains
> 192.168.1.10:/cdrom /nfscdrom nfs rsize=1024,wsize=1024 0 0
>
> i on the server, i then did... /e
oh, the test thing is because initially i thought it might have been a
problem with trying to export a cdrom. and i made a test dir and
export. anyhow, i switched it back to the cdrom in both cases.
thneed:~# rpcinfo -p
program vers proto port
102 tcp111 portmapper
On Wed, 14 Mar 2001, Forrest English wrote:
> ok, here's what i do on the server.
>
> /etc/exports file contains
> /cdrom 192.168.2.30
>
> and the client's fstab contains
> 192.168.1.10:/cdrom /nfscdrom nfs rsize=1024,wsize=1024 0 0
>
> i on the server, i then did... /etc/init.d/nfs-serv
no change. same results.
--
Forrest English
http://truffula.net
"When we have nothing left to give
There will be no reason for us to live
But when we have nothing left to lose
You will have nothing left to use"
-Fugazi
On Thu, 15 Mar 2001, Fabio Massimo Di Nitto wrote:
> Forrest English w
Forrest English wrote:
>
> ok, here's what i do on the server.
>
> /etc/exports file contains
> /cdrom 192.168.2.30
>From my experience it has to look like this:
/cdrom 192.168.2.30/255.255.255.255(ro)
192.168.2.30 is the ip address allowed to remote mount the cdrom
255.255.255.2
On Thursday 30 November 2000 13:04, robert_wilhelm_land wrote:
> Keeping temporärly away from NIS I added user "rland" on MINI to group
> "users". On GOOFY user "rland" belongs only to group "users".
>
> After this "rland" on MINI may view the files and do a ls -l, but he
> cannot write to the moun
Robert Guthrie <[EMAIL PROTECTED]> wrote:
> On Thursday 30 November 2000 12:07, robert_wilhelm_land wrote:
> > two linux boxes are connected via nfs to each other:
> >
> > MINI (kernel_2.2.17) <--> GOOFY (kernel_2.0.38)
> >
> > the /etc/exports on GOOFY: /home/rland MINI(rw)
> >
> >
> >
>
On Thursday 30 November 2000 12:07, robert_wilhelm_land wrote:
> two linux boxes are connected via nfs to each other:
>
> MINI (kernel_2.2.17) <--> GOOFY (kernel_2.0.38)
>
> the /etc/exports on GOOFY: /home/rland MINI(rw)
>
>
>
> After rebooting I do a
> MINI:/home/rland# mount -t nfs GOO
> "Colin" == Colin McMillen <[EMAIL PROTECTED]> writes:
Colin> Anyone have any ideas on what's going wrong, and what I can
Colin> try to fix it?
I sometimes get these errors, and then suddenly everything comes
good.
ie. the same behaviour I might expect if I pulled the network plug o
One possibility is that the client is not named what you think. Try to
telnet from the client to the NFS server and do a 'who' and see what it
thinks the clients hostname is. You are exporting to myclientname but
the server may be seeing it as myclientname.domain.nam and that won't
match causing t
Jean Pierre LeJacq <[EMAIL PROTECTED]> writes:
> I'm having problems getting Solaris 2.5.1 to use the Debian NFS
> server. Read only file systems work fine. On read-write file
we'll go the other way round in the near future ;-)
but Solaris uses a new nfs Version (3) instead of 2. Perhaps you c
I do have similar problems serving SGI machines.
It might depend on the way a file system is mounted
e.g. hard vs. soft, but I'am not sure, still testing ...
Markus Diesmann
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL
31 matches
Mail list logo
