From: Christopher Huhn <C.Huhn@gsi.de>
To: nfs@lists.sourceforge.net
Subject: executable but not readable
Date: Thu, 25 Mar 2004 19:00:18 +0100 [thread overview]
Message-ID: <40631E32.1020707@gsi.de> (raw)
Hi alltogether,
(I'm sorry to bother you with this but I could not find any clues yet)
Szenario:
* a server exports shell scripts to clients with root_squash
* these scripts have -rwx-r-x--x (root:root) rights (executable but
not readable)
The clients are able to run these scripts with server kernel version 2.4.20.
Now we switched the server to 2.4.25 and get "permission denied" on
execution.
As far as I comprehend file permissions this should never have worked?
But nobody ever noticed as long as it worked and the guy in charge says:
"This was always a feature on VMS." :-P
This assumption is confirmed by the fact that "su nobody -c
/usr/local/sbin/mkclonediskremupdate" executed on the server does not
work either.
Are these observations correct or am I missing something?
Sorry for the silly question.
Regards,
Christopher
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-03-25 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 18:00 Christopher Huhn [this message]
2004-03-25 18:37 ` executable but not readable Trond Myklebust
2004-03-26 10:48 ` Christopher Huhn
2004-03-26 19:17 ` Trond Myklebust
2004-03-27 12:17 ` Frank van Maarseveen
2004-03-28 23:46 ` Trond Myklebust
2004-03-28 23:59 ` Frank van Maarseveen
2004-03-29 1:00 ` Trond Myklebust
2004-03-29 11:35 ` Christopher Huhn
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=40631E32.1020707@gsi.de \
--to=c.huhn@gsi.de \
--cc=nfs@lists.sourceforge.net \
/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.