Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!bloom-beacon!eru!luth!sunic!mcsun!ndosl!fdmetd!steinar From: steinar@fdmetd.uucp (Steinar Overbeck Cook) Newsgroups: comp.databases Subject: SIGTERM, SIGINT from ORACLE's shadow process. Keywords: SIGTERM SIGINT ORACLE daemons Message-ID: <522@fdmetd.uucp> Date: 20 Oct 89 13:45:21 GMT Organization: Fellesdata a.s, Oslo, Norway Lines: 24 In the Installation and Users guide for Oracle V5 it says that ORACLE uses the signals SIGINT, SIGPIPE and SIGTERM to send signals from the shadow process to the user process. The manual states that SIGTERM is "Used by the Pipe Driver to resynchronize communication between the user and ORACLE after an error or interrupt." This is fine, but *what* sort of errors makes the shadow process send SIGTERM. I have a daemon which is connected to an ORACLE database, but if I close all open files at startup (Which all good daemons should do), after a while I get SIGTERM from the shadow process when I do some fork/execs in my server. Does anyone have a list of when ORACLE's shadow process will signal SIGTERM ? Any help would be greatly appreciated. -- Steinar Overbeck Cook, Fellesdata a.s, P.O. Box 248, 0212 OSLO 2, NORWAY Phone : +47 2 52 80 80 Fax : +47 2 52 85 10 E-mail : ...!mcvax!ndosl!fdmetd!steinar or steinar@fdmetd.uucp