Re: Reducing KODRETRY

Matt Ackeret <[email protected]> writes:

> >>mAybe instead you could make pine "realize" that there's one suspended in
> >>the background, and print that out?

Yes, I guess I could do that but I'm guessing that would require me to dig more
into the innards of the source.  I'm happy enough just to quit the current
instance without having to wait an unreasonable time to do it.

> >No. What if the two pines run on different hosts? :)
> 
> oh ok, I guess I misunderstood.
> 
> I had thought you ^Z-ed out of pine, then typed pine again at the shell.

Yes, that's what my problem was (I orginated the thread).  It's strange that
I don't run into this problem when I suspend pine on one host, then run pine
on another.  I don't understand why it tries so hard to recover a local lock
but it's quite happy to run on another host.

> >I'd suggest using the 'mbx' format on the server; I did
> >the switch and ever since, I can have 2 or even 3 pines
> >accessing the same folders simultaneously. Of course, I
> >don't know if you can change that.

(Adressing Thorsten) I'll take your word for it that it would solve the
problem, but converting hundreds of my user mailbox formats just to solve
this one problem is using a case of sledgehammer killing flies.  If I had
to change formats, I would Maildir instead.

> I have no idea what the format on the server is -- I use IMAP, and it works
> fine with multiple clients simultaneously..  But I thought you were
> using IMAP too, so I guess I don't quite see what's causing the timeout.

I am using Unix mbox format.  That was my concern: if I lower KODRETRY,
I would break something else.  I did remake libc-client.so and included it
in my personal LD_LIBRARY_PATH, and it seems to work: it shortens the lock
bailout time to something bearable.

Joseph Tam <[email protected]>
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info