access to stat from open() call

I notice that when I strace a perl script that has an open() call, a
stat call is made. Is there anyway to access this information to avoid
doing a second stat call?

Alternatively, is there a way to turn a fd returned from POSIX::open
into a perl filehandle without having a stat call performed?

thanks,
eric

.

Relevant Pages

  • Re: stat() bug
    ... > While debugging a Perl script, I came across a statement like this: ... since the documentation doesn't say what stat() does when called ... I'm not filing a bug because of this. ... "Reply" at the bottom of the article headers. ...
    (comp.lang.perl.misc)
  • Re: stat() bug
    ... > While debugging a Perl script, I came across a statement like this: ... > I know that this is not the proper usage of the stat function, ... Since the entire operation is being done in scalar context (that is, ... you are assigning to the scalar variable $foo, ...
    (comp.lang.perl.misc)
  • Re: access to stat from open() call
    ... > I notice that when I strace a perl script that has an opencall, ... > stat call is made. ... I have seen cases when an error occurs and it does descend. ...
    (comp.lang.perl.misc)
  • Re: [linux-cifs-client] [PATCH] Remove information leak in Linux CIFS clientg
    ... Just merged into the cifs-2.6 tree, changing the last patch as you ... just suggested to take out the logged path name. ... than strace on stat of a local file does (which also returns access ... You can't strace a process you don't own. ...
    (Linux-Kernel)
  • Re: [linux-cifs-client] [PATCH] Remove information leak in Linux CIFS clientg
    ... than strace on stat of a local file does (which also returns access ... You can't strace a process you don't own. ... That is an information leak and imho a privacy problem. ...
    (Linux-Kernel)