From: Stuart D Gathman <stuart@bmsi.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM volume umask change
Date: Sun, 14 Nov 2010 18:00:24 -0500 [thread overview]
Message-ID: <4CE06A08.1050209@bmsi.com> (raw)
In-Reply-To: <606057079.20101114024527@snet.sk>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On 11/13/2010 08:45 PM, Marek Soha wrote:
> When I create file/directory in LVM volume, it is created with
> permissions (mode) 666. I need to get 644.
> I changed umask in /etc/lvm/lvm.conf, but it did not helped.
> Any ideas?
lvm.conf has nothing to do with any filesystems (and associated files
and directories) you might happen to create on a logical volume.
Your question is a basic unix question. Try "man umask".
[-- Attachment #2: Type: text/html, Size: 833 bytes --]
next prev parent reply other threads:[~2010-11-14 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 1:45 [linux-lvm] LVM volume umask change Marek Soha
2010-11-14 23:00 ` Stuart D Gathman [this message]
2010-11-14 23:28 ` Marek Soha
2010-11-15 1:06 ` Eugene Vilensky
2010-11-15 1:29 ` Marek Soha
2010-11-15 2:17 ` Eugene Vilensky
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=4CE06A08.1050209@bmsi.com \
--to=stuart@bmsi.com \
--cc=linux-lvm@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).