SCIENTIFIC-LINUX-USERS Archives

November 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Paul Robert Marino <[log in to unmask]>
Reply To:
Paul Robert Marino <[log in to unmask]>
Date:
Sat, 29 Nov 2014 13:18:38 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (48 lines)
Mahmood
you will also probably need to learn about the setgid bit.



On Sat, Nov 29, 2014 at 12:23 PM, Nico Kadel-Garcia <[log in to unmask]> wrote:
> On Sat, Nov 29, 2014 at 10:56 AM, Mahmood N <[log in to unmask]> wrote:
>> Hi
>> A server and a client both run SL6.3. On server, I have exported a disk with
>> the following property
>>    /data 192.168.1.0/24(rw,sync,no_root_squash)
>>
>> and on the client side, I wrote this entry in the fstab
>>    192.168.1.5:/data       /data                   nfs     defaults     0 0
>>
>> However on the client side, I am not able to create folders.
>>
>> [mahmood@client data]$ mkdir afolder
>> mkdir: cannot create directory `afolder': Permission denied
>>
>> However, root has the write permission.
>>
>> [root@client data]# mkdir a
>> [root@client data]#
>>
>> How can I grant the write permission tot he user?
>>
>> Regards,
>> Mahmood
>
> You need to learn about "uid", "gid", and file system permissions.
> "The user" and "the groupo" that own a file are stored, on the NFS
> serrver's file system, as numbers. Those numbers are tied to group and
> owner as far as the login name and login user's groups by
> "/etc/passwd", "/etc/group", and lots of different network tools that
> can also do that.
>
> If the user name on the client *has the same uid and group gid
> memberships* as the server expects, then they'lll typically have
> permission to write to those directories. This is much like file
> ownership on a local directory. If someone else owns the directory,
> *and did not allow write access to others*, others will not be able to
> write there.
>
> In this case, I would do "ls -al /data" and see who owns it. Then I'd
> look up the man pages for "chown" and "chgrp" and "chmod" to get a
> handle on what you want to allow and prevent.

ATOM RSS1 RSS2