in reply to Re: Problems creating Crypt::OpenPGP standalone exe
in thread Problems creating Crypt::OpenPGP standalone exe

I had all but given up hope. I can't thank you enough. Works great!!!! Any sugguestions on controlling how much CPU the process can take?
  • Comment on Re: Re: Problems creating Crypt::OpenPGP standalone exe

Replies are listed 'Best First'.
Re: Re: Re: Problems creating Crypt::OpenPGP standalone exe
by PodMaster (Abbot) on Mar 22, 2004 at 13:15 UTC
    Why with use less 'CPU'; of course. Seeing how that's currently unimplemented (but it could be windows -- hmm, this should be a wishlist item for PAR), you'll have to do it like
    cat foowithlesscpu.bat cmd.exe /c start /LOW foo.exe
    or write it in perl with Win32::Process.

    I should note that it should only be CPU intensive only on the 1st run when par has to extract all the modules ... after that they're cached (then it's as cpu intensive as it takes encode the message).

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

      Never mind, I got it. Thanks for all the help.

      boat73