All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Aron Griffis <aron@hp.com>, xen-devel@lists.xensource.com
Subject: Re: PATCH: Remove execute permission from xend-debug.log
Date: Tue, 24 Apr 2007 23:35:14 +0100	[thread overview]
Message-ID: <20070424223514.GA31537@redhat.com> (raw)
In-Reply-To: <C2544396.63EB%Keir.Fraser@cl.cam.ac.uk>

On Tue, Apr 24, 2007 at 11:30:30PM +0100, Keir Fraser wrote:
> On 24/4/07 23:15, "Aron Griffis" <aron@hp.com> wrote:
> 
> >>> Seems that the patch should be using 0666 instead of 0600 so that
> >>> umask can affect group/other perms.  At the very least it should use
> >>> 0664.
> >> 
> >> Xen-debug.log is the only file in /var/log/xen getting created with
> >> +x permissions, so something is obviously up. Arguably we can get
> >> rid of xend-debug.log entirely -- I don't believe anything ever gets
> >> logged there these days. I took the patch because 0600 seems saner
> >> than 0755.
> > 
> > It doesn't make any real difference to me, just thought I'd bring up
> > the umask question before the patch was committed... though at this
> > point it's in staging, so I guess I was too late. ;-)
> 
> You're probably right that one of 0644,0664,0666 is better. They're
> certainly more in line with all other files under /var/log/xen.

Yeah, actually I agree - I thought the other files were already 0600, but
in fact it is just the directory itself whose permissions are restricted.
I'd just go for 0666, so if an admin wants to make the log files accessible
to non-root, they merely have to change the permissions on the dir itself
and the files will already be correctly setup. It was only removing the
executable bit that I really wanted to sort out.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

      reply	other threads:[~2007-04-24 22:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 19:22 PATCH: Remove execute permission from xend-debug.log Daniel P. Berrange
2007-04-24 21:39 ` Aron Griffis
2007-04-24 21:45   ` Aron Griffis
2007-04-24 22:08     ` Keir Fraser
2007-04-24 22:15       ` Aron Griffis
2007-04-24 22:30         ` Keir Fraser
2007-04-24 22:35           ` Daniel P. Berrange [this message]

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=20070424223514.GA31537@redhat.com \
    --to=berrange@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=aron@hp.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.