Quick update for all who were good enough to reply.
My problem is now solved...for any others wishing to
"secure" their servers in such a fashion, here is what
it was..
1. /usr/bin/yppasswd needs to be other executable.
2. even with the above done, if I login as one use,
then su to root and then
#snip#
passwd needs to run setuid root, so it can write the
new password to
/etc/master.passwd:
[homer: danielby: ~]$ ls -l `which passwd`
-r-sr-xr-x 2 root wheel 32824 19 May 11:04
/usr/bin/passwd*
You need to re-enable the setuid bit.
#end-snip#
That's not it I'm afraid. The setuid bit w
not issue the passwd command
without getting :-
passwd: permission denied
Does anyone know what other commands passwd may be
trying to execute, or of any way I can 'trace' the
program to see what it's trying to do (I've KTRACE
switched OFF in the kernel and have no intention of
sw
hecked using 'df' on the
emergency shell, it had filled up the small memory disk rather than writing
to the real disks mounted under /mnt/...
I've now "back-tracked" and installed 4.7-RELEASE using the same mechanisms
on the same two machines and they work without an
