RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1122993 - perl-homedir.csh causes login error with CSH if PERL_HOMEDIR=0 is set
Summary: perl-homedir.csh causes login error with CSH if PERL_HOMEDIR=0 is set
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: perl-local-lib
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 7.1
Assignee: perl-maint-list
QA Contact: Martin Kyral
Lenka Špačková
URL:
Whiteboard:
Depends On:
Blocks: 1018952 1289025 1298243 1305230 1380363
TreeView+ depends on / blocked
 
Reported: 2014-07-24 14:32 UTC by Thomas Buchner
Modified: 2020-09-10 09:19 UTC (History)
13 users (show)

Fixed In Version: perl-local-lib-1.008010-4.el7
Doc Type: Release Note
Doc Text:
The *perl-homedir* profile scripts now support *csh* Previously, the *perl-homedir* profile scripts were unable to handle the *C shell* (csh) syntax. Consequently, when the the _perl-homedir_ package was installed and the `/etc/sysconfig/perl-homedir` file contained the `PERL_HOMEDIR=0` line, executing the profile scripts resulted in the following error: PERL_HOMEDIR=0: Command not found. This update adds support for the *csh* syntax, and the described problem no longer occurs.
Clone Of:
Environment:
Last Closed: 2017-08-01 18:14:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Potential patch for /etc/profile.d/perl-homedir.csh (656 bytes, text/plain)
2014-07-24 14:32 UTC, Thomas Buchner 		no flags Details
Fix (2.09 KB, patch)
2014-07-25 07:25 UTC, Petr Pisar 		no flags Details | Diff
Fix (2.09 KB, patch)
2014-07-28 08:31 UTC, Petr Pisar 		no flags Details | Diff
Show Obsolete (2) View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1921 0 normal SHIPPED_LIVE perl-local-lib bug fix update 2017-08-01 18:06:28 UTC

Description Thomas Buchner 2014-07-24 14:32:11 UTC 
Created attachment 920563 [details]
Potential patch for /etc/profile.d/perl-homedir.csh

Description of problem: 
If the file /etc/sysconfig/perl-homedir contains the line PERL_HOMEDIR=0, users with CSH as login shell will an error during login: "PERL_HOMEDIR=0: Command not found." and the directory gets created anyways.


Version-Release number of selected component (if applicable):
perl-homedir-1.008010-3.el7.noarch


How reproducible:
always


Steps to Reproduce:
1. Put the line PERL_HOMEDIR=0 into /etc/sysconfig/perl-homedir
2. useradd -s /bin/csh test
3. su - test


Actual results:
PERL_HOMEDIR=0: Command not found.
Attempting to create directory /home/emroot/perl5
[test@host]$

Expected results:
No error message and the directory ~/perl5 will not get created.


Additional info:
The file /etc/sysconfig/perl-homedir is in BASH syntax and works perfectly for users with BASH as login shell. The CSH script /etc/profile.d/perl-homedir.csh simply sources the file and thus runs into an error due to syntax mismatch. An eval line is needed instead of a simple source (patch for working solution attached).
Comment 2 Petr Pisar 2014-07-25 07:08:49 UTC 
Indeed. The configuration files have to be parsed to be useful for csh profile script. Thank you for the report and the patch.
Comment 3 Petr Pisar 2014-07-25 07:25:58 UTC 
Created attachment 920863 [details]
Fix
Comment 4 Petr Pisar 2014-07-25 07:34:49 UTC 
How to test:

(1) Install perl-homedir and tcsh packages.
(2) Create /etc/sysconfig/perl-homedir with "PERL_HOMEDIR=0" content and run a tcsh as log-in shell:
Before:
  "PERL_HOMEDIR=0: Command not found." error message is printed and the
  PERL_HOMEDIR variable is set to 1 in the shell.
After:
  No error message is printed and the PERL_HOMEDIR variable is set to 0.
(3) Remove the /etc/sysconfig/perl-homedir, create ~/.perl-homedir with "PERL_HOMEDIR=0" content and run a tcsh as log-in shell. The results should be the same as in (2).
Comment 5 Petr Pisar 2014-07-25 07:51:35 UTC 
Thomas, could you please report this issue to the Red Hat support. Doing so increases chance that this fix will be approved as it will be recognized as a customer-facing problem.
Comment 6 Petr Pisar 2014-07-28 08:31:08 UTC 
Created attachment 921723 [details]
Fix

This sed(1) resides in /bin/sed, not in /usr/bin/sed. The wrong path would break dependency solver.
Comment 20 errata-xmlrpc 2017-08-01 18:14:01 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1921
Note You need to log in before you can comment on or make changes to this bug.