Subject: Rebuildning .lu all the time

From: Jeffrey Goldberg <[email-masked]>
Date: Wed, 7 Aug 1996 11:21:14 +0100

The first time I compose a message each session (or actually the
first time Pine needs to use the global address book), I get
a warning that I cannot write in the directory which contains
the global address book .lu file, and then there is a substantial
wait.

Why is pine trying to write in that directory?  I believe that
the .lu file is up to date.

-j

--
Jeffrey Goldberg                +44 (0)1234 750 111 x 2826
 Cranfield Computer Centre      FAX         751 814
 [email-masked]     http://WWW.Cranfield.ac.uk/public/cc/cc047/
"I am much fonder of my critics than I am of my fans."  --Thomas Kuhn (d 1996)

---

From: Jeffrey Goldberg <[email-masked]>
Date: Wed, 7 Aug 1996 12:01:31 +0100 (BST)

On Wed, 7 Aug 1996, Mike Brudenell wrote:

> Presumably you are mistaken in your belief: hence why Pine is trying to
> rebuild the file.  (Note that the format used in the .lu file changed
> between Pine 3.91 and 3.93, and may have changed again to 3.95 (I don't
> know as I have installed the latter yet)).

Ah hah!  I haven't rebuilt the .lu file after installing 3.95.  So
that it is.  I should have thought of that.  Thanks.

-j

---

From: Mike Brudenell <[email-masked]>
Date: Wed, 7 Aug 1996 11:51:10 +0100 (BST)

Get the person who looks after the global addressbook to update the .lu
file (using the "pine -create_lu" command: its options are described in
the man page for Pine).

Cheers,

Mike Brudenell                                         <[email-masked]>
------------------------------------------------------------------------
The Computing Service, University of York, Heslington, York, YO1 5DD, UK
Tel: +44-1904-433811  FAX: +44-1904-433740  http://www.york.ac.uk/~pmb1/

---

From: [email-masked] (Zachary H Leber)
Date: Wed, 7 Aug 1996 11:48:36 GMT

I had a similar problem when switching between different versions of Pine. 
If multiple people access the same addressbooks with different versions,
the .lu files will get rewritten.  No good solution I found.

---

From: Rudolf Kompf <[email-masked]>
Date: Wed, 7 Aug 1996 15:00:55 +0200 (MET DST)

> the .lu file is up to date.
After weeks ago I got this effect, but MY .lu was NOT ok. I remember (?) that
I found the actual .lu file built by pine in the /tmp directory. After
copying onto the normal .lu file: All ok.

-----------------------------------------------------------------------
Rudolf Kompf                     | E-mail: [email-masked]

---

From: Mike Brudenell <[email-masked]>
Date: Wed, 7 Aug 1996 16:12:28 +0100 (BST)

There is a solution, providing that when you build a particular version of
Pine you modify the string which contains the name of the global
configuration files.  These are usually "pine.conf" and "pine.conf.fixed".
However I modify these strings to include the version number of Pine: for
example "pine.conf-3.91" and "pine.conf.fixed-3.91".

This then allows you to have different configuration files for each
version of the Pine binary you have in use on your system: quite useful as
newer releases often have new features (which admittedly the old version
would probably just ignore) which you want to test out before inflicting
(sorry! RELEASING) them on your users.

You can then modify the systemwide global addressbooks listed in each
configuration file so that the different versions of Pine access separate
global addressbook files (and hence their associated lookup files).

A cunning trick is to use UNIX's "ln" command to link the address book
files themselves together so that it is only one file, but accessed
through two or more names.  This eases keeping the data in step, and you
then just have to remember to recreate the associated .lu file for each
name by which the data file is known.

Of course this only helps with global address books specified in the
systemwide configuration file(s); it doesn't help people who have them
listed explicitly in their personal (.pinerc) preference files.  However
the thought may be of use to some...

Cheers,

---

From: Jeffrey Goldberg <[email-masked]>
Date: Wed, 7 Aug 1996 17:55:44 +0100

> that it is.  I should have thought of that.  Thanks.

Um.  It still doesn't work.  Is there some tool I can use to
check the consistance of a .lu file?

-j

---

From: Les Wallis <[email-masked]>
Date: Thu, 8 Aug 1996 12:41:05 +1000 (AEST)

Can you not solve this by starting pine with the -P option to point to
differing pine.conf files? These files could contain reference to
differing addressbooks, each one accessed by groups of people using the
same versions of PINE?