Date: Sun, 26 Dec 2004 00:04:17 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 484 ************************************************** Saturday 25 December 2004 Number 484 ************************************************** Subjects for today 1 Re: CC1.EXE & SYS3176 : Stefan.Neis at t-online.de 2 POVRAY : John Poltorak 3 Re: LIBC 6 b2 - pipe and sockets : Knut St. Osmundsen" 4 Re: Merrry Christmas was LIBC 6 b2 - pipe and sockets : lsunley at mb.sympatico.ca **= Email 1 ==========================** Date: Fri, 24 Dec 2004 14:30:35 +0100 From: Stefan.Neis at t-online.de Subject: Re: CC1.EXE & SYS3176 Hi, > I've also just got a system trap:- > > Exception in device driver: > TRAP 000e > > It doesn't mention which device driver which is strange. Was it a > particular kernel which started providing more useful information? > I'm currently using Int. rev. 14.062_W4 on the machine having problems. From the current readme include in kernels from testcase: (snipp) 20020515 revision 14.089d (note the new naming convention) (snipp) PJ28603 module name missing or incorrect in r0 trap screen (snipp) So it seems like you'd need at least 14.089d to reliably get more useful information on trap screens. Regards, Stefan **= Email 2 ==========================** Date: Fri, 24 Dec 2004 16:15:26 +0000 From: John Poltorak Subject: POVRAY Has anyone tried building a recent version of POVRAY on OS/2? -- John **= Email 3 ==========================** Date: Sat, 25 Dec 2004 01:22:22 +0100 From: "Knut St. Osmundsen" Subject: Re: LIBC 6 b2 - pipe and sockets lsunley at mb.sympatico.ca wrote: > Hi all, > > I noticed that you cannot use a pipe in a select() statement. > > Is this an error or a limitation? Known limitation. Someone was supposed to look into selecting on non-socket handles... > The code in postgreSQL allocates a couple of pipes for stats data > collection and then attemtpts to use the pipe handle in select(). This > returns a -1 error with a message of "invalid parameter". That's right. > I adapted the win32 work around for the equivalent problem to OS/2 to > avoid the error. The work around consists of allocating a couple of > sockets to 127.0.0.1 to act as pipes. Btw. on some unixes pipes are local unix sockets. :-) Kind Regards, knut **= Email 4 ==========================** Date: Fri, 24 Dec 2004 23:43:26 -0500 From: lsunley at mb.sympatico.ca Subject: Re: Merrry Christmas was LIBC 6 b2 - pipe and sockets Thanks and Merrry Christmas to all....... Lorne -- ----------------------------------------------------------- lsunley at mb.sympatico.ca -----------------------------------------------------------