Thanks to all those who made suggestions. Among the many suggestions were to include scripts in rc0.d to trace what was going on. Because the system is not yet a production system I created a script K00crash to force a dump (taken from Panic) #!/bin/ksh # # used to force a system dump # Nick Hindley 12/6/2001 # echo "`date`: Forcing a crash!" adb -k -w /dev/ksyms /dev/mem <<! rootdir/X rootdir/W 0 $q ! Digging in the process table showed nothing funny... I also set auto-boot? to false to keep the system down and attached a matrix printer to a vt220 and again I got nothing. Finally, out of desparation, I enabled accounting and after wading through the mass of data using acctcom finally found the offending shell script - installed by one of out suppliers. The information contained in this e-mail is intended for the recipient or entity to whom it is addressed. It may contain confidential information that is exempt from disclosure by law and if you are not the intended recipient, you must not copy, distribute or take any act in reliance on it. If you have received this e-mail in error, please notify the sender immediately and delete from your system.Received on Thu Jun 14 12:02:09 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:24:57 EDT