Subject: problem with pine hanging....

From: Fred Clift <[email-masked]>
Date: Tue, 9 Mar 1999 09:29:30 -0700 (MST)

I'm runing pine 4.05 under solaris and hpux.  Pine's global conf file
is set to log in to a local imap server by default, so that when you
start pine, it prompts for username and password.

Up until recently, this worked just fine, but now pine seems to hang
for a little less than a minute before presenting the log in prompt.
After that all works fine, but it's very annoying to wait 1 minute to
read email...

(other imap clients ie dtmail under solaris dont have this problem --
they connect right away...  And pine exhibits this problem under both
platforms, solaris and hpux...)

So, I started up pine with verbose debugging (pine -d 9)

and then watch the .pine-debug1 file with tail -f.

Eventually after pine reads all the config files, I get to a point where
it does the following

About to open folder "INBOX"    inbox: "INBOX"
busy_alarm(1, Opening "INBOX", 0, 1)
q_status_message(Opening "INBOX"     )
output_message(Opening "INBOX"     )
STATUS cmd:120, max:1, min0
SIGCHLD raised
alarm_signal()
alarm_signal()
alarm_signal()
alarm_signal()
alarm_signal()
....

During the 'pause' in pine, one of these alarm_signal() lines per
second, approximately, appears...

Eventually

...
alarm_signal()
IMAP 14:42:19 3/8 mm_log babble: Trying IP address [MY-IP_DELETED]
IMAP DEBUG 14:42:20 3/8: * OK MAILSERVER.hostname.deleted IMAP4rev1 
Service 9.0(159) at Mon,
 8 Mar 1999 14:26:28 -0700 (MST) (Report problems in this server to 
[email-masked]
ington.EDU)

(note that I changed the IP and hostname of the mail server so
spambots wont pick em out of this message)

Any ideas what gives?  I'm about to download the code and start
editing the configuration files that end in .c ... if you know what I
mean...

I just heard a report from another user that ocasionally any remote 
folder write is very slow for him -- kind of bursty -- dont  know if 
this problem is realted.

--
Fred Clift - [email-masked] Systems Manager - Computer Science - BYU
Remember: if brute force doesn't work, you're just not using enough.

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Daniel Sands <[email-masked]>
Date: Wed, 10 Mar 1999 11:23:26 -0700

Over here, this was due to the network taking a VERY long time to figure out
that RSH was not permitted.  Pine first tries to RSH to the mail machine and
run rimapd to bypass sending your name and password over the network in the
clear.  When this fails, it falls back to normal IMAP.  I guess one possible
reason for this is a firewall that drops RSH packets.

I had to tell it not to use RSH.  In file c-client/tcp_unix.c, change line 41
to:
static long rshtimeout = 0;     /* rsh timeout */

Note:  If "rshtimeout" is not on line 41, use the line that it is on, and
change its value to 0.

---

From: Juhani Sivusalo <[email-masked]>
Date: Wed, 10 Mar 1999 20:57:46 +0000

On Wed, 10 Mar 1999, Daniel Sands wrote:

> that RSH was not permitted.  
> 

Or fix 'rsh-open-timeout=0'  .pinerc in home directory.
It should disable rsh.

-- 
     Juhani Sivusalo            E-Mail: [email-masked]
       Oulu, Finland          http://www.netppl.fi/~jasivu/
       phone: +358-8-520 8523         GSM: +358-400-582 546

---

From: Daniel Sands <[email-masked]>
Date: Wed, 10 Mar 1999 12:22:41 -0700

> Or fix 'rsh-open-timeout=0'  .pinerc in home directory.

That would work for one user.  Would be better to store that in the pine.conf
file.