patchThe GNU Bourne-Again SHell - Patches: patch #1775, Mail spool is accessed even when...


You are not allowed to post comments on this tracker with your current authentication level.

patch #1775: Mail spool is accessed even when MAILCHECK unset or negative

Submitter:  Invalid User ID <#21379>
Submitted:  Tue 29 Jul 2003 04:11:23 PM UTC
Category:  None Priority:  5 - Normal
Status:  Invalid Privacy:  Public
Assigned to:  jaalto Open/Closed:  Closed

Thu 08 Oct 2009 08:18:05 AM UTC, comment #1: 

This does not seem to relate to bash. No bug report content, no patch. Closing.

Jari Aalto <jaalto>
Group administrator
Tue 29 Jul 2003 04:11:23 PM UTC, original submission:  

Patch motivation:

Bash  has a mail checking feature that, by default, checks your mail
spool file every 60 seconds (or 600 if you have POSIXLY_CORRECT
set).  You can disable this feature by unsetting your MAILCHECK
environment variable or setting it to a negative value.
However, even if you do this, bash will still check the timestamp and
file size of your mail file when it first starts in interactive mode
as well as when any of the MAIL, MAILCHECK, and MAILPATH environment
changes value.  The end result is that every time you start
an interactive bash shell, your mail file is checked.  For systems
where the mail spool directory is mounted via NFS or some other
network file system, this behavior can become a performance drag on
both the client and server.

If you're a wireless laptop user, you don't want to wait for the
automounter to mount the mail spool every time you open a shell
window. Worse, if the NFS server goes down, you may not be able to log
in to a client, even with a local account, because bash will hang on
an I/O operation while trying to check your mail.  Therefore, it is
desirable to make bash not stat the mail file at all when MAILCHECK
is unset MAILCHECK or set it to a negative value.  Bash shouldn't
examine our mail file at all unless we change the value of
MAILCHECK back to a non-negative value.

This patch implements the above behavior without affecting the normal
behavior for non-negative values of MAILCHECK.  Someone more intimate
with the bash architecture may have a prettier way to implement the

Invalid User ID <#21379>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by jaalto (Posted a comment)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-10-08 jaalto Open/ClosedOpen Closed
    2009-10-08 jaalto StatusNone Invalid
        Assigned toNone jaalto

    Back to the top

    Powered by Savane 3.12.
    Corresponding source code