Re: Why doesn't chmod work on this lexical filehandle?

Replies are listed 'Best First'.
Re^2: Why doesn't chmod work on this lexical filehandle? by williff (Initiate) on Feb 14, 2011 at 21:56 UTC
Thanks for great suggestions. Moved close after chmod but it did not help. Working on Linux box, uname -a says: Linux ... 2.6.9-89.0.16.ELxenU #1 SMP Tue Oct 27 04:12:25 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux chmod returns 0 and $! returns "No such file or directory" even after moving close after chmod. will investigate globs, glob refs. I think those are used in main, but a scalar ref was used with this sub.	[reply]
Re^3: Why doesn't chmod work on this lexical filehandle? (error) by tye (Sage) on Feb 15, 2011 at 06:24 UTC
Then it sounds like $OUT is being interpreted as a string and that that string is being interpreted as a file name: If chmod had thought that you had passed a file handle to it on a system where Perl doesn't think fchmod() is supported, then it would have died rather than returning 0. If you passed a file handle to chmod() on a system with fchmod, "No such file or directory" could not have been the failure reason. - tye	[reply]
Re^3: Why doesn't chmod work on this lexical filehandle? by Anonyrnous Monk (Hermit) on Feb 15, 2011 at 07:49 UTC
Most likely, your Perl is too old. From perldelta of 5.8.8: chdir, chmod and chown can now work on filehandles as well as filenames, if the system supports respectively `fchdir` , `fchmod` and `fchown` , thanks to a patch provided by Gisle Aas. See also Re^2: Why doesn't chmod work on this lexical filehandle?	[reply] [d/l] [select]
Re^4: Why doesn't chmod work on this lexical filehandle? by williff (Initiate) on Feb 15, 2011 at 15:23 UTC
Yes! This is the problem. Our default perl at /usr/local/bin/perl is a symlink to 5.8. When i pointed to the latest version installed, which was 5.10.1, then the code works great. Thank you. And thanks to all Perl Monks sharing their wisdom and debug tips.	[reply]