You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compiling Perl and running ./perl harness in directory t yields
uid=NNN topuid=10 euid=MMMM path='/afs/desy.de/user/d' at ../../lib/File/Temp.pm line 688.
File::Temp::_is_safe("/afs/CELLNAME/user/U", SCALAR(0x17475f0)) called at ../../lib/File/Temp.pm line 787
File::Temp::_is_verysafe(".", SCALAR(0x17475f0)) called at ../../lib/File/Temp.pm line 479
File::Temp::_gettemp("tmpXXXXX", "open", 1, "mkdir", 0, "unlink_on_close", 0, "suffixlen", ...) called at ../../lib/Fil
e/Temp.pm line 1488
File::Temp::tempfile("tmpXXXXX", "UNLINK", 1) called at t/security.t line 105
eval {...} called at t/security.t line 105
main::test_security() called at t/security.t line 67
../cpan/File-Temp/t/security.t ....................................... ok
when compiled within AFS filesystem, but works fine on a local filesystem. ./Configure detects AFS and displays a notice AFS may be running... I'll be extra cautious then... and AFS is somewhat peculiar concerning ACL handling. Permissions are handled directory-wise (file permissions are not considered like in e.g. ext4); see also https://docs.openafs.org/UserGuide/HDRWQ46.html
If I understood everything correctly, this patch should help:
Compiling Perl and running
./perl harness
in directoryt
yieldswhen compiled within AFS filesystem, but works fine on a local filesystem.
./Configure
detects AFS and displays a noticeAFS may be running... I'll be extra cautious then...
and AFS is somewhat peculiar concerning ACL handling. Permissions are handled directory-wise (file permissions are not considered like in e.g. ext4); see also https://docs.openafs.org/UserGuide/HDRWQ46.htmlIf I understood everything correctly, this patch should help:
The text was updated successfully, but these errors were encountered: