> At 05:46 PM 7/9/05 +0200, [EMAIL PROTECTED] wrote: > >But DBD-MySQL doesn't seem to work 100 % correct with fork because > Windows > >reports an error with perl and kills it. This seems to occur at random. > >Sometimes it happens after 100 updates, sometimes after 1000 or even > 10000 > >updates. > > I experienced a similar problem with Open3(), perl would crash at random. > Apparently there is something unstable about Windows's forking mechanism > (actually I don't think it truly forks). I never found a solution to > that, > I just ran large numbers of processes so that the task would finish even > with an ultra high mortality rate. I had a similar MySQL project where I > had to drastically speed things up over one process. I did it by having > multiple independent processes. I had a scheduled task which fired off a > shell script which launched 10-15 copies of the script per machine. MySQL > was smokin off the rails. If ur crashing problem is fork related that > should get around it. >
I had the some thought as a possible solution. But my problem is, the updates result from a select and lots of calculations. Not using fork would mean to dub the environment myself and pass it somehow to those other processes. I think using commandlineparamters is not relieable and using socket-communications to do it is lots of work. I think, the best approach will be to look for a linux server and port my whole project to it... Harry _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
