Edmund R. MacKenty wrote:
Grega then goes on to describe his woes with db2fmcd, which is exactly the same behavior I've had it do to me, with no apparent cause and at very random and unfortunate times. There's actually a very simple solution, which I wish the DB2 team would consider, because it is the UN*X way of doing it. Instead of starting it from init, start db2fmcd from the DB2 rc-script, along with the other admin tools. When db2fmcd starts up, it should immediately spawn off a child process that does all the work. The parent should do nothing but wait around for its child to die, and can then loop to start up another one in its place. The parent process is very robust because it only executes a very tiny bit of code. That's the UN*X way of implementing a daemon that keeps itself alive. Had they just done that simple thing, we'd all be happy with it, and their installer would have been easier to write, and all kinds of goodness follows.
and users' sysadmins could stop the thing without changing inittab or changing runlevel. Some people, and developers come to mind, want to stop it sometimes. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
