Gnus development mailing list
 help / color / mirror / Atom feed
From: Markus Linnala <maage@cs.tut.fi>
Subject: filepermissons
Date: Mon, 22 Jan 1996 15:40:55 +0200	[thread overview]
Message-ID: <199601221341.PAA08744@viitatiainen.cs.tut.fi> (raw)


Is there a way to make all .newsrc* stuff permanently unreadable to
group & others? I know what umask is. I don't want to change it.

*dribble and *~ files get their permissions from umask, not from
.newsrc as I'd like them to get.

How about variable gnus-keep-newsrc-permissions. It should keep
.newsrc* permissions according to .newsrc.

--
//Markus


             reply	other threads:[~1996-01-22 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-22 13:40 Markus Linnala [this message]
1996-01-22 15:45 ` filepermissons Karl_Kleinpaste
1996-01-23 15:57 ` filepermissons Lars Magne Ingebrigtsen
1996-01-23 18:02   ` filepermissons Colin Rafferty
1996-01-25 20:08     ` filepermissons Lars Magne Ingebrigtsen
1996-01-25 21:19       ` filepermissons Colin Rafferty
1996-01-26 16:46         ` filepermissons Lars Magne Ingebrigtsen
1996-02-01 16:58           ` filepermissons Hallvard B Furuseth

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=199601221341.PAA08744@viitatiainen.cs.tut.fi \
    --to=maage@cs.tut.fi \
    /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).