Does MHonArc do any kind of testing for directory permissions before
doing anything?
I'm asking because I recently set up some archives using v2.2.0
in AFS. AFS totally ignores the 'og' settings for files and
directories when it comes to permissions because it uses its
own authentication scheme and access control lists.
Anyhow, when the target directory had permissions set to rwx------
(which is perfectly valid in AFS because the process had a token
that gave it permission to write there), MHonArc would say
ERROR: Unable to access /afs/ncsa/web/internal/htdocs/lists/email/aug98
Other shell scripts would do their stuff just fine -- it was
only when MHonArc tried doing things in the directory. I ended
up changing the directory to rwxrwxrwx (which in AFS is functionally
the same as rwx------), but it's still somewhat annoying.
Is there any harm in turning this off? It looks like it's all around
line 198 in mhopt.pl... Ideally this would be a commandline flag
so that we could share the same binary for AFS and non-AFS use.
Maybe something like -checkperms?
Comments?
Chris
