If the -d44.4 debugging switchis specified, this error is
printed:
[slink mode mode] EPERM
If the SFF_REGONLY flag is set, the file must be a regular file. If it is not, it is rejected, and
-d44.4 causes the following to be printed:
[non-reg mode mode] EPERM
If wantmode has the write bits set, and the existing file has any execute bits set, the file is
rejected and -d44.4 causes the following to be printed:
[exec bits mode] EPERM
If the file has more than one link, the file is rejected and -d44.4 causes the following to be
printed:
[link count nlinks] EPERM
If the SFF_SETUIDOK flag is specified, if SUID_ROOT_FILES_OK (?§3.4.63 on page 146)
was defined when sendmail was compiled,* if the file exists, if it has the set-user-id bit set in
the mode but no execute bits set in the mode, and if it is not owned by root, sendmail
performs subsequent checks under the set-user-id and set-group-id identities of the existing
file. A similar process occurs with the set-group-id bit. Sendmail then prints:
[uid new_uid, stat filemode, mode wantmode ]
If access is finally allowed, sendmail concludes with:
OK
Otherwise, it concludes with:
EACCES
15.7.55 -d44.5
Trace writable( ) Debug command-line switch
The -d44.5 debugging switchdisplays the values passed to sendmail??™s internal writable( )
routine. This routine nearly duplicates the function of the access(3) call?? but does it much
more safely and allows checks to be made under the identity of the controlling user:
writable(fname, sff_flags)
Here, the fname is the full pathname of the file being checked.
Pages:
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014