Re: prevent multiple start of app
- From: reppisch <spam@xxxxxxxxxxx>
- Date: Tue, 28 Feb 2006 08:44:58 +0100
Kasper Dupont schrieb:
reppisch wrote:It's not a security issue, it's a service problem.
Upgrading is not an option.
Sometimes it is necesarry.
Certified?
We have some boards for telephony (not for the consumer market) which are more expensive than the pc they are in.
The hardware vendor does only guarantee (and will process incident reports) for them if they run in a very well specified enviroment.
The enviroment is RH7.2 with some patches applied.
If we bought a new 'driver' release (which is expensive and provides unneeded features) we may have something more recent as a base OS.
In any other configuration you are completely on your own and i have no intentions to shoot myself in the foot that way ;-)
---
Btw. I also need gcc which supports the __thread storage class. I think this was introduced in 3.3. (i don't want to clutter the code with getspecific/setspecific calls)
I compiled gcc 3.3 from the source tarball but something is missing. Maybe the binutils... The gcc33-compiled a.out crashes with illegal instruction. I think this is because of the different ABI which changed from glibc 2.2 to 2.3.
.
- References:
- prevent multiple start of app
- From: reppisch
- Re: prevent multiple start of app
- From: "Nils O. Selåsdal"
- Re: prevent multiple start of app
- From: reppisch
- Re: prevent multiple start of app
- From: Larry I Smith
- Re: prevent multiple start of app
- From: reppisch
- Re: prevent multiple start of app
- From: reppisch
- prevent multiple start of app
- Prev by Date: Re: libc/printf bug
- Next by Date: Re: prevent multiple start of app
- Previous by thread: Re: prevent multiple start of app
- Next by thread: ov518, xawtv and green image
- Index(es):