>Although I haven't seen exactly the problem you describe, I have seen >generally strange behaviour with MacHTTP PCGI's when I try to edit one that >is running. If I tweak a CGI and re-run it, I get multiple copies of it in >the Applications menu, and after the next reboot several "Rescued items" in >the trash which are PCGI's. That is because the CGI process that is running is compiled from a different source; you edited the source, so it has to recompile. >I also found that with the new version of MacPerl I can edit a CGI with >BBEdit by selecting the "Edit with BBedit..." menu, but if I try to save it >in BBEdit the file gets corrupted. That's because BBEdit can't read or >write in the PCGI format. BBEdit can open the CGI only through the MacPerl >menu, which causes MacPerl to read the file and send the data to the BBEdit >window. > >This mans that if you want to use BBEdit to edit PCGI scripts, you have to >get the BBEdit file you want to save back to a MacPerl window, before you >can save it as a PCGI. This can be done easily through AppleScript. > >Basically you open the file in MacPerl with the "Edit with BBedit..." menu, >then when you are finished editing it in BBEdit you select a menu item in >BBEdit that moves the contents of the window back to MacPerl. Not the most >elegant, but I can't think of any better way given the current >architecture. Actually, I have been quite successful just hitting Save in BBEdit and having MacPerl do the rest of the work to save it in the MPCGI format, but only when the CGI process is not running. #================================================================ perl -e 'srand();if(rand>.5){$i=0;foreach(@ARGV){@$i=split(//);$z [$i]=0;foreach$l(@$i){$s[$i][$z[$i]]=$l;$z[$i]++;}$i++;}foreach$m (@s){foreach$g(@{$m}){print$g}print" ";$m++}}else{print(join(" ", @ARGV))}print"\n"' McClellan Clan Motto: Think On Chris Nandor pudge@pcix.com PGP Key 0xB76E72AD http://pudge.petersons.com/