From: Padraig Brady (padraig.brady at domain corvil.com)
Date: Fri 06 Sep 2002 - 11:39:28 IST
Colin Nevin wrote:
> Hi All,
> I have a question which is a bit tricky and was
> wondering of anyone has come across this problem
> before or could point me in the right direction.
> I am involved in porting a SCO unix application to
> Linux, and we have encountered a problem with the way
> semaphores are being handled.
I would guess that the "error" values returned
are not being processed correctly. I think his would
be the main source of differences between SCO and Linux
if there were any.
info libc "Interrupted Primitives" might have
also have pertinent info?
> I have also noticed that if I introduce a slight delay
> between changing semaphore states the problem goes
> away, but this causes our entire application to run
> really sloooww !! lol
Think that's bad! Eircell bought a mad
mainframe class machine from Compaq (GS160) to
run their billing app faster. But it ran at exactly
the same speed for some reason. I was called in
and promptly found a sleep(1) synchronisation
between 2 processes! So much for throwing hardware
at a problem.
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:18:42 GMT