Matty wrote:
On 3/2/07, Michael Shapiro <[EMAIL PROTECTED]> wrote:
One is the Fault Management architecture, running inside of fmd(1M),
which
knows how to diagnose cpu failures based on error telemetry and disable
bad CPUs. The other is the interrupt distribution daemon, intrd(1M),
which tries to keep interrupt mappings distributed appropriately.
And the third is powerd(1M), which does E-* compliance power
management of
many things, including disks and CPUs.
Just out of curiosity, is there a reason intrd was written in Perl?
The fellow who wrote it liked perl? poold is written in perl and
merging was/is anticipated?
Perl wouldn't be my first choice for intrd's implementation language,
but it wouldn't be my last, either.
Also, is there a reason intrd lives in /usr/lib instead of
/usr/lib/intrd?
I reckon there are reasons for the choice of location
and lanugage, but I can't seem to find a PSARC case that describes
them.
PSARC doesn't often weigh in on implementation language selection unless
it involves interface issues. If intrd was written in C, it would
change nothing about how one interacts with it.
As to directory, lpsched, pcmciad, utmpd, gpilotd, esd, etc,
are in /usr/lib.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[EMAIL PROTECTED] http://blogs.sun.com/barts
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
