Christopher Smith wrote:
Okay, if the OS can't clean up file handles, sockets, and memory when
your process dies, I very much doubt you're going to have much luck
doing so in some catch block. Similarly for your database with database
transactions. Seriously, process death is about as safe a way as you can
find to clean up from an undefined error.
Actually, this particular bit of wisdom is contrary to my personal
experiences. We had several systems running Solaris that would do things
like *not* clean up memory after processes exited, overwrite inodes with
the contents of directories, and so on. I actually wrote Tcl code to
watch whether Solaris had stopped cleaning up memory on process exit and
queued a notification scheduled a reboot when I saw it happening. On the
other hand, we never encountered an error in Tcl during the entire
lifetime of that company.
--
Darren New / San Diego, CA, USA (PST)
His kernel fu is strong.
He studied at the Shao Linux Temple.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
