Bug 22317 - $TMOUT set to read-only but /etc/security/shell tries to set it
Summary: $TMOUT set to read-only but /etc/security/shell tries to set it
Status: RESOLVED DUPLICATE of bug 16356
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Shlomi Fish
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-04 16:02 CET by Frank Griffin
Modified: 2018-01-05 13:41 CET (History)
2 users (show)

See Also:
Source RPM: bash
CVE:
Status comment:


Attachments

Description Frank Griffin 2018-01-04 16:02:36 CET
Sometime in the past few days something updated cauldron to set the bash variable $TMOUT to read-only.  The only problem with that is that /etc/security/shell, which is run whenever .bashrc is sourced, tries to set it to 0 and produces an error message about TMOUT being read-only.

Commenting out the assignment gets rid of the message.  It seems to be set to 0 anyway.  

Presumably it is being set read-only to prevent something else from setting it to a nonzero value, but either that something else should be changed or else /etc/security/shell should be changed.
Comment 1 Bit Twister 2018-01-05 10:49:39 CET
FYI: bug 16356

CC: (none) => bittwister2

Comment 2 Marja Van Waes 2018-01-05 11:38:41 CET
Assigning to the registered bash maintainer.

Assignee: bugsquad => shlomif
CC: (none) => marja11
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=16356

Comment 3 Frank Griffin 2018-01-05 13:41:38 CET
Dup of bug#16356

*** This bug has been marked as a duplicate of bug 16356 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED


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