From: "Josh N. Pritikin" <jpab+@andrew.cmu.edu>
To: rc@archone.tamu.edu
Subject: file protections
Date: Fri, 24 Apr 1992 20:32:10 -0500 [thread overview]
Message-ID: <Ydy=OOW00awPFMj0U_@andrew.cmu.edu> (raw)
In-Reply-To: <9204241746.aa01849@ceres.srg.af.mil>
At CMU we use AFS a great deal. I've run into was seems to be a bad
interaction between AFS and rc. Consider this program:
$ C:/inc/graphlib>ll glclock
-rwx------ 1 14061 0 319488 Apr 24 18:22 glclock*
I log into the CS cell get my tokens with klog so I have access to
this program in the Andrew cell. Thus, even though I don't own the
file or have access to it via the rwx flags, I should be able to run
it, however,
C:/inc/graphlib>./glclock
./glclock: Permission denied
[status 1]
Now if I,
C:/inc/graphlib>sh
$ ./glclock
It works fine. Is this fixable without special casing for AFS?
joshp
prev parent reply other threads:[~1992-04-25 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-04-24 21:46 rc and readline and SIGINT Tom Culliton x2278
1992-04-25 1:32 ` Josh N. Pritikin [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='Ydy=OOW00awPFMj0U_@andrew.cmu.edu' \
--to=jpab+@andrew.cmu.edu \
--cc=rc@archone.tamu.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).