C-Isam and error 004 (interrupted system call)

Posted in 2000

Claudius Lengl — Wed, 12 Jul 2000 19:44:53 +0200 — source: Informix-list mailing list archive (1991-1998)

Using the c-isam getnext/isnext routines the task sometimes breaks resulting error 004. Just sometimes. :-( I have this problem on different machines (AIX, SINIX, Solaris), running with SE 5.x and SE 7.x. Can anybody help me? Thanks in advance Claudius Lengl (C.Lengl@ixpert.de)

↪ replying to Claudius Lengl

mars1972@my-deja.com — Wed, 12 Jul 2000 18:14:01 GMT — source: Informix-list mailing list archive (1991-1998)

The problem could be any number of things. Do you have a sysadmin getting kill happy? Do you have an alarm() call in the code that is going off during the isnext? Are you listening to a socket and recieve a message during the isnext? Any of these will result in an interrupted system call. Something to try is to set up a signal handler that will report what signal was recieved. In article <8kiap4$1d7e$1@euler.space.net>, "Claudius Lengl" <C.Lengl@ixpert.de> wrote: > Using the c-isam getnext/isnext routines the task sometimes breaks resulting > error 004. > Just sometimes. :-( > I have this problem on different machines (AIX, SINIX, Solaris), running > with SE 5.x and SE 7.x. > > Can anybody help me? > > Thanks in advance > > Claudius Lengl (C.Lengl@ixpert.de) > > -- # unrm / ksh: unrm: not found # man cpio Sent via Deja.com http://www.deja.com/ Before you buy.