Re: Coprocess
Brought to you by:
ftobin
|
From: Frank T. <ft...@ui...> - 2000-08-02 14:41:06
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Billy Donahue, at 12:26 -0400 on Tue, 1 Aug 2000, wrote: > I'm still thinking about the startup time of pgpenvelope. > It's all the perl compiling. It would be nice to have > a persistent perl process running 'hot' alongside pine, > The problem is killing it when pine dies. I guess pine > would be the parent pid or something... Actually, it wouldn't be a problem; I'd simply have pgpenvelope call pine, so it would wrapper around the pine session, exiting when pine exited. > So there would be this daemon running for you, and > there would be a short connector program which would be > the actual pine filter. Well, it's not easy, and I > haven't thought it out too well, but I thought I'd see > if anyone else is/was thinking about it. Yes, I've thought about it, and it is a good idea, and it can probably be implemented decently. This is an important issue (especially for me on a p200 :) ), but I have to research the issue. BTW, hopefully you are using the procmail filter now; it certainly helps on incoming mails :) - -- Frank Tobin http://www.uiuc.edu/~ftobin/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.2 (FreeBSD) Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/ iEYEARECAAYFAjmIMv8ACgkQVv/RCiYMT6MS+wCdFxjQTqo3lAcKydDWHlnOfc6P lZ4Anj5fRDSpDfA3IIfZDOFlO8XujodO =Z19l -----END PGP SIGNATURE----- |