We [exec a 160K program about once a second with no ill effects. Very very rarely we have had a stuck exec process that goes CPU bound. I'm assuming it's some kind of race condition in the start/stop interface. So we run a monitor program to watch for this and kill it.
Good luck, Jim > > Hi. > > Our company runs one AOLserver instance which is mainly used (almost no > HTTP requests) for handling email messages. > > We want to use mks_vir (a virus software very popular in Poland), which > we would use doing > set handle [open "|mks32 --filelist-on-stdin" a+] > and then send the actual filename upon receiving an email (which is > actually sent via a temporary file - so we would just send mks the > filename). > > I'm however wondering about possible problems with fork'ing the mks > process? Some memory issues? Potential problems? > > -- > WK > (written at Stardate 56684.6) > > "Data typing is an illusion. Everything is a sequence of bytes." > -Todd Coram >
