New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong Perl's chmod behavior #17139
Comments
From v.99cygwin@gmail.comCreated by v.99cygwin@gmail.comPerl's chmod command sets wrong permissions. There is a workaroud with vlado@allex:~$ rm -f file{1,2} ; perl -e 'sub t{open vlado@allex:~$ getfacl . file{1,2} # file: file1 # file: file2 vlado@allex:~$ umask Same wrong permissions sets previous version of Perl, perl 5, version Perl Info
|
From choroba@matfyz.czThe 666 must be octal, not decimal. Replacing your command with chmod 0o666, "file1"; fixes the issue. Ch. |
The RT System itself - Status changed from 'new' to 'open' |
From @xenuOn Fri, 30 Aug 2019 13:21:43 +0200 (CEST)
chmod 0666, "file1" Unlike Raku, Perl doesn't have "0o" syntax. |
From @khwilliamsonRejecting, as the number the OP was passing to chmod wasn't the actual value passed |
@khwilliamson - Status changed from 'open' to 'rejected' |
From v.99cygwin@gmail.comOn 30.8.2019 13:36, Tomasz Konojacki via RT wrote:
Thank you. Sorry for noise. |
Migrated from rt.perl.org#134389 (status was 'rejected')
Searchable as RT134389$
The text was updated successfully, but these errors were encountered: