public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Subdirectories on NFS server missing 'executable' permission
Date: Sun, 27 Jan 2013 18:23:07 +0200	[thread overview]
Message-ID: <20130127182307.58236760@khamul.example.com> (raw)
In-Reply-To: <51046CCC.1030508@seichter.de>

On Sun, 27 Jan 2013 00:54:52 +0100
Ralph Seichter <gentoo-user@seichter.de> wrote:

> On 27.01.13 00:04, Alan McKinnon wrote:
> 
> > What sort of client is this, and what umask is it using?
> 
> The client is an Edision Argus Pingulux Plus satellite receiver.
> 
> [root@stlinux]#uname -a
> Linux stlinux 2.6.32.42_stm24_V4.1-SAT7111_7111-STSDK #56 PREEMPT Tue
> Oct 16 16:17:14 CST 2012 sh4 GNU/Linux
> 
> > That's regular shell umask, not some fancy thing related to fs
> > mounts.
> 
> [root@stlinux]#umask
> 0022
> 
> This umask looks OK to me.
> 
> -Ralph
> 

You config certainly looks right to me, and I don't know of any config
that makes it work differently.

I've always found default permissions on NFS shares to be a difficult
thing to implement. One can do it with POSIX file attributes on the
server but I always found that cumbersome and very susceptible to being
forgotten about

I usually end up running chmod in a cron on the server :-)

-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2013-01-27 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26 16:13 [gentoo-user] Subdirectories on NFS server missing 'executable' permission Ralph Seichter
2013-01-26 23:04 ` Alan McKinnon
2013-01-26 23:54   ` Ralph Seichter
2013-01-27 16:23     ` Alan McKinnon [this message]
2013-01-27 17:46       ` Ralph Seichter
2013-01-27 18:21         ` Alan McKinnon
2013-01-27 20:09           ` Ralph Seichter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130127182307.58236760@khamul.example.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox