Hello all
I'm working on developing a network server program at the moment, and I'd
like to make it as stable and reliable as problem. So far, I've been
messing around with threads, forks etc. Basically what I want to do is
span a new thread to handle each new client connection. I'm using threads
to handle this part. The problem is that I further want each thread to
execute another seperate program, which the spawned thread can then
control using signals or some other IPC. So far I'm planning on doing this
using a fork from within the thread. The problem is that I'm a bit fuzzy
on the overheads etc associated with threads, forks etc. So basically,
what are the problems with architecture outlined above, and is there a
better way of doing it?
Thanks all
Patrick
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!