>Well, the immediate problem is that when su(1) called
>initgroups(3), which is part of the process of changing
>your identity, it returned an error of EPERM. Given your
>previous crisis, I'd suspect you missed changing the
>ownership on something somewhere, or a file mode got
>changed as well somewhere.
>
>You might try running an strace(1) on /bin/su and looking
>at the arguments that are getting passed to the low-level
>system calls. You might find some clues there.
i alREaDY SaiD tHat - WHeN HE CHAngED THe owneRShIp
on /BIn/Su THe seTuid BIt GOT AUtomaTICALLy clEAred;
WHEN He chaNgEd owNErshIp baCK TO rOOT tHE SetUid bIt
rEMaiNeD CLeAR. It'S TRIvIAl to DEMoNSTRate; cLEar ThAt
BiT on yOUR owN /BIN/Su ANd YOu'Ll seE pRECiselY The
SAME ErRoR meSsaGe He's is seEInG. shEeSh! iT'S aS
iF yOU gUyS dIdn'T REaD MY MEsSaGe OR SOMETHing...
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
