summaryrefslogtreecommitdiff
path: root/pod/perlport.pod
diff options
context:
space:
mode:
authorCraig A. Berry <craigberry@mac.com>2018-01-14 13:42:05 -0600
committerCraig A. Berry <craigberry@mac.com>2018-01-15 07:00:40 -0600
commit669d6ad81497efd33243c692e6f057f97c6c1567 (patch)
treee207b7f5dd9c5e606e5999c8941447597edac7a5 /pod/perlport.pod
parentd75174cd2be6a6a63099d496f8f3efc6995f933d (diff)
downloadperl-669d6ad81497efd33243c692e6f057f97c6c1567.tar.gz
VMS does have fchmod and fchown.
The test for fchmod in t/io/fs.t does, however, reveal a wrinkle that is also true of chmod on VMS: a mode argument of zero does not mean turn off all permisions but rather set permissions to the user's default. This is probably an ancient behavior from pre-standard days. For now, just skip the affected test and document what's different.
Diffstat (limited to 'pod/perlport.pod')
-rw-r--r--pod/perlport.pod4
1 files changed, 4 insertions, 0 deletions
diff --git a/pod/perlport.pod b/pod/perlport.pod
index 36c217d4ec..45158d58d6 100644
--- a/pod/perlport.pod
+++ b/pod/perlport.pod
@@ -1591,6 +1591,10 @@ in the SYSTEM environment settings.
Setting the exec bit on some locations (generally F</sdcard>) will return true
but not actually set the bit.
+(VMS)
+A mode argument of zero sets permissions to the user's default permission mask
+rather than disabling all permissions.
+
=item chown
(S<Plan 9>, S<RISC OS>)