Rich Smrcina writes:
>DB2 does the same thing, yuck.
>
>David Boyes wrote:
>> On Wed, Nov 16, 2005 at 02:03:52PM +0800, John Summerfied wrote:
>> Let's not push them too hard. Parts of Tivoli are still discovering
>> /etc/init.d for startup scripts (editing /etc/inittab directly
>> ... *shudder*).
Actually, DB2's use of /etc/inittab is for a good reason: it wants to
respawn a process if it ever dies, and init will do that properly. The
inittab really needs a form of "directory include" capability so that
packages can drop snippets of inittab instructions into separate files.
But I don't think anyone wants to change how init works.
The alternative, of course, is for DB2 to come with its own little
respawner process to make sure that its db2fmcd daemon stays around.
Actually, they have a real problem with that daemon going haywire sometimes
on some systems (AIX here), so I wish they would make a respawner that
killed it off and restarted it too every now and then. That would at least
hide whatever bug is in that daemon.
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software, Inc.
Newton, MA USA
----------------------------------------------------------------------
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
