Maybe. For general things, that depends on your OS. Some OSses can give users roles, and you really fine-tune, which system calls may be executed by whom.

To give read only access one some file to some people, one can use ACLs, which is implemented on many OSses. To check if a file exists, one would have to be given read/exec access to the directory. And you need read access to the file to determine whether it's a file, or something else.

If it comes to -x and frieds, ACLs aren't going to help you, as they look at the permission bits.

Now, for the given problem, I don't understand why you need more than read-only rights. All you need for -f and -e is read only access anyway.

In reply to Re: perl file status and sudo by JavaFan
in thread perl file status and sudo by Saved

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.