Re: crash on solaris

>Jul 25 11:11:27  xinetd[12323]: [ID 385394 local0.crit] 
>12323 {mem_fault_handler} Address of fault: 4
>
>This happened unexpected and very rare. Any ideas ?

Something is pointing to 0. You might want to go into
signals.c and add:

#define DEBUG 1

so that xinetd generates a core dump. Then look at it with
dbx or gdb and see if you can get a backtrace. Be sure to
leave the debug symbols in xinetd. Without a bactrace, I
have no idea where it happened.

The other thing to note, what were the differences between
the old version of xinetd.conf & the new version of
xinetd.conf that made you want to send USR2? There might be
a clue in that.

And lastly, USR2 is deprecated for generating a reload. The
man page says use HUP. We might reassign USR2 to something
else one of these days so you may want to update scripts or
operational proceedures.

Best Regards,
-Steve Grubb

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com