From: Greg Chavez (greg.chavez@gmail.com)
Date: Fri Feb 11 2005 - 09:30:32 EST
I am working short-term at a client site that relies heavily on remote
CDE logins between their many Suns. The system on which I am working
is a Sun Blade 2500 running Solaris 9, fully patched, JASS'd, and
running HP OpenView Operations .. I built the OS myself. The gist is
that /dev/null keeps getting turned into an empty file with 664
permissions. Attempts to relink /dev/null to the null pseudo device
last only until someone tries to perform a remote CDE login. The
culprit appears to be /dev/dtremote which is symlinked to /dev/null.
That would seem to be a problem to me, but this old post suggests
otherwise:
http://marc.theaimsgroup.com/?l=sun-managers&m=104009118018389&w=2
As long as I change /dev/null from 644 to 666, this seems to cause no
problems when the system is running. But this causes huge problems
when the system is rebooted. Nothing can "create" /dev/null and the
systems boots up in single-user, read only. I have to mount the OS
from CD and relink /dev/null to the psuedo device to get it working
again. Obviously, this is terrible.
Does anybodh have any insight into this? If I can't figure it out,
I'm going to advise my client to not remote-CDE into this box which,
really, I should advise them to not do anyway. Nevertheless. They
like things to work.
Thanks, will sum.
--Greg Chavez
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:09 EDT