Problem
The man page for setluid(S) states that this function will return
-1 and set errno to EPERM if the LUID (login user ID) has already
been set prior to the call. This behavior only applies if the
kernel parameter SECLUID has been set. In "Traditional" (and "Low")
security mode, SECLUID is not set by default. In this case,
root may successfully change the LUID through a call to setluid(S)
even if the LUID has already been set. Only in "High" security
mode is SECLUID set. In this case, once the LUID has been set,
it cannot be changed, and any subsequent call to setluid(S) will
return -1 and set EPERM.NOTE: Only root is authorized to set the LUID through setluid(S). Solution
This documentation omission has been reported to SCO Engineering.
See also
ta 115442 "Cron jobs don't run after installing OSS642A on a system in high security mode."