Diego wrote:

2008/10/11 corvid <corvid@lavabit.com>

...

Jorge wrote:

...

On Sat, Oct 11, 2008 at 01:40:00AM +0000, corvid wrote:

...

...

2) No dpi stuff would work until I copied in a dpidrc file.

...

Is something supposed to make it for me, or is there something I'm overlooking that is supposed to tell me how to make one if I didn't already have one? (I know that I got the proto.* lines from mail that Diego sent out last year when that stuff changed, but I don't remember how I knew originally to put in a dpi_dir line.)

Please give it a look and send me a patch.

I don't do much shell scripting, so I'll send it to the list...

Do the script solve that problem? Do your dillo use system wide or user directory dpis?

For me it did. This is with user dir dpis.

dpid can(or must) work the old way without a service/handler list in dpidrc, but dpid needs (even before) the system dpi dir (dpi_dir=/usr/.../lib/dillo/dpi/) in dpidrc.

The tricky thing about dpis is that... once it works, it works, but there seem to be many different failure modes depending on how many pieces one has correctly gotten into place. (I set up local dpis twice last year, and both times it took a little while to make it all happy.) So far as I could tell last night, no dpidrc gave cryptic errors, an empty dpidrc gave a good message about needing a dpi_dir (and seemed to find my dpis), putting in the dpi_dir line made it stop working again, and adding the proto lines made it work -- but then it all depends on whether a dpid started more or less successfully in previous attempts, and the same with the dir in /tmp/, and the dpi_socket_dir, etc., etc.... I would try to delete partially-made things in an effort to return to the same state, but probably not completely successfully.