Subject: Re: Pine 4.10 problem

From: Pine Versions <[email-masked]>
Date: Thu, 11 Mar 1999 14:19:30 -0500 (EST)

We have just upgraded one of our unix office servers to Pine 4.10. So far
 everything seems to work fine but one thing. When 2 sessions of Pine are
 open by the same id, the second session is put into 'read only'. The tech
 notes under folder locking leads us to believe that the second session
 will put the first session in read only. Pine 3.96 works this way which it
 should be.
 Are we doing something wrong or is this a bug? Because if this is the case
 then there will be problems if the first session of Pine was aborted
 somehow and then the person logged on again. They will not be able to do
 anything until the first session times out.
 We are running Solaris 2.6 on a Sun machine. We did a Build with  DEBUG=''
 and so5 parameters.
 When you reply, would you please also include  the  'cc'?
 
 Thanks
 -----------------------------------------------------------------------------
 Jessie Kleefstra                    E-Mail:[email-masked]
 Sr.Consultant, Helpdesk Services           [email-masked]
 Computing & Information Services     Phone: (905) 525-9140  ext. 24357
 McMaster University, ABB-132           Fax: (905) 528-3773
 ------------------------------------------------------------------------------

---

From: "Richard L. Eisenman" <[email-masked]>
Date: Thu, 11 Mar 1999 12:43:13 -0800 (PST)

We've noticed the same problem with 4.10 under DU.  We'd also like to
know how to work around this.  

>  When you reply, would you please also include  the  'cc'?

Richard Eisenman
Supervisor, Computing and Telecommunications
W.S.U. Tri-Cities, CIC 225E
Office (509) 372-7381
Fax (509) 372-7281
[email-masked]
http://www2.tricity.wsu.edu/richardeisenman
http:///www2.tricity.wsu.edu/ctc

---

From: Mike Brudenell <[email-masked]>
Date: Thu, 11 Mar 1999 21:29:31 +0000

This was asked (and answered) a week or two back in this same forum.

Apparently it is a (now!) known bug in the Pine 4.10 kit.  It will be fixed
in the next release.

If you are willing to build the programs from scratch then you can fix your
Pine and IMAP daemon as follows:

1.  Grab the latest IMAP kit (which is separate from the Pine kit).

2.  Build this: it will give you a fixed C-client library and a fixed IMAP
    daemon.

3.  Rebuild your Pine, linking it against the above C-client library rather
    than the one from the Pine kit.

Test/install the rebuilt IMAP daemon and Pine executables.

Cheers,

Mike B-)
-- 
The Computing Service, University of York, Heslington, York Yo10 5DD, UK
Tel: +44-1904-433811  FAX: +44-1904-433740  http://www.york.ac.uk/~pmb1/

* Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

--On Thu, Mar 11, 1999 12:43 pm -0800 "Richard L. Eisenman"
<[email-masked]> wrote:

>>  We have just upgraded one of our unix office servers to Pine 4.10. So
>>  far everything seems to work fine but one thing. When 2 sessions of
>>  Pine are open by the same id, the second session is put into 'read
>>  only'. The tech notes under folder locking leads us to believe that the
>>  second session will put the first session in read only. Pine 3.96 works
>>  this way which it should be.
>>  Are we doing something wrong or is this a bug? Because if this is the
>>  case then there will be problems if the first session of Pine was
>>  aborted somehow and then the person logged on again. They will not be
>>  able to do anything until the first session times out.
>>  We are running Solaris 2.6 on a Sun machine. We did a Build with
>>  DEBUG='' and so5 parameters.
>>  -----------------------------------------------------------------------
>>  ------ Jessie Kleefstra
>>  E-Mail:[email-masked] Sr.Consultant, Helpdesk Services
>>  [email-masked] Computing & Information Services     Phone: (905)
>>  525-9140  ext. 24357 McMaster University, ABB-132           Fax: (905)
>>  528-3773