Bug 9736 - maildir patch for Pine is bogus
Summary: maildir patch for Pine is bogus
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pine   
(Show other bugs)
Version: 6.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: pine
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-02-24 06:47 UTC by wingc
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-27 15:52:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description wingc 2000-02-24 06:47:37 UTC
The 'maildir' patch included in the Red Hat 6.1 and 6.2beta pine RPM causes
some very undesirable behavior. It causes pine to do a recursive stat of
files in your home directory.

If you have a recursive symlink in your home directory, Pine will die
instantly when you ask for a folder list:

redhat6.2% cd
redhat6.2% ln -s ~ maildirsucks
redhat6.2% pine

[ press 'l' ]

Problem detected: "Received abort signal".
Pine Exiting.

If you strace pine, you will notice that it is trying to recursively stat
every file in your home directory up to 3 levels deep.

This is bad.

If your home directory has a lot of files in it, and is mounted over a
network, this is unbelieveably bad.

This either needs to get fixed, or else the maildir patch should be removed
from Pine. (isn't the patch really intended to be used on the server end,


Chris Wing

Comment 1 Trond Eivind Glomsrxd 2000-04-11 16:24:59 UTC
I can't reproduce it like that, but:

Add a new user

Make a symlink, "ln -s ~ foobar"

Run pine to create the mail directory

exit pine

Go to $HOME/mail

Make a new symlink:

ln -s ~ foobar

Go to your home directory

Run pine, use "l"

Comment 2 Trond Eivind Glomsrxd 2000-04-27 15:52:59 UTC
I've removed the maildir patches - look for 4.21-13 or higher in the next

Comment 3 david 2000-10-01 22:11:11 UTC
Fixed in Bug # 18038.

Note You need to log in before you can comment on or make changes to this bug.