There could also be fairly-serious problems lurking if many copies of your web page get launched at the very same time. It is sometimes difficult to actually have a web-page "do something" like this. You can't control how many copies may be started at once, and remember also that HTTP is "stateless." Finally, bear in mind that Apache is usually run as nobody, with no permissions to do much of anything at all, and that there's a good reason for that . . . Maybe re-think this idea.
in reply to Forking SSH via Apache