sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Scott Schwartz <schwartz@galapagos.cse.psu.edu>
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: umask
Date: Thu, 30 Mar 1995 20:14:49 -0500	[thread overview]
Message-ID: <95Mar30.201457est.12683@galapagos.cse.psu.edu> (raw)

I run with 022, but some things I'd rather have tighter
control over.  Sam makes temp files at various times that
don't really need to be group or world writable.
Hence this suggestion:

===================================================================
RCS file: RCS/mesg.c,v
retrieving revision 1.1
diff -r1.1 mesg.c
83c83
< 		fd = create("/tmp/sam.out", 1, 0666L);
---
> 		fd = create("/tmp/sam.out", 1, 0600L);
===================================================================
RCS file: RCS/sam.c,v
retrieving revision 1.1
diff -r1.1 sam.c
153c153
< 			io = create(buf, 1, 0777);
---
> 			io = create(buf, 1, 0700);
===================================================================
RCS file: RCS/shell.c,v
retrieving revision 1.1
diff -r1.1 shell.c
37c37
< 			fd = create(errfile, 1, 0666L);
---
> 			fd = create(errfile, 1, 0600L);



                 reply	other threads:[~1995-03-31  1:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=95Mar30.201457est.12683@galapagos.cse.psu.edu \
    --to=schwartz@galapagos.cse.psu.edu \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    /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).