Re: dmesg output: application bug dbaccess XXXX

On 11 Feb, 15:48, "June Nebab" <jne...@idealcut.com> wrote: > Folks, > > I get the following message when running 'dmesg': > >    application bug: dbaccess(xxxx) has SIGCHLD set to SIG_IGN but calls > wait(). >  (see the NOTES section of 'man 2 wait').  Workaround activated. > > Google pointed me to this link > (http://www.iiug.org/library/linux/linux_faq/english/iolfaq-5.html).  Is > this message the same bug #97893?  The workaround posted in the link is for > IDS7.X.   Yes we are using sockets ("soctcp") for database connetions. > > Intel redhat enterprise linux v 3 > IDS 9.4UC8 > > Any helpful information is appreciated. > > DISCLAIMER > > This transmission and the information contained herein and/or in any attachments hereto and/or in any attachments thereto is privileged and/or confidential and is intended ONLY for the use of the individual(s) and/or entity(s) named above. If you are not the intended recipient, you are strictly prohibited from disclosing, printing, copying, using or disseminating this transmission and/or any such attachments and any information contained in this transmission and/or in any such attachments. ANY unauthorized interception of this transmission and/or any such attachments is a violation of federal criminal law. > If you have received this transmission in error, please notify the sender immediately and delete the transmission and all such attachments. Looks like a harmless issue, migrate to a later version of dbacess or open a case with IBM.