Bug 144984 - .bash_logout file is different depending on how user created
Summary: .bash_logout file is different depending on how user created
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: bash (Show other bugs)
(Show other bugs)
Version: 3
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-13 14:09 UTC by John Horne
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-13 14:58:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description John Horne 2005-01-13 14:09:04 UTC
Description of problem:
Created a non-user account during the installation process. Once FC3
fully installed and rebooted then created another account using
'useradd' command. The .bash_logout file is different in each account.

The installation account .bash_logout file has the size of 24 bytes,
as does the root account one. The account created by useradd uses the
.bash_logout in /etc/skel, and this has a size of 302 bytes since it
includes gpm code.

Version-Release number of selected component (if applicable):
bash-3.0-18
shadow-utils-4.0.3-56
kernel-2.6.10-1.737_FC3

How reproducible:




Steps to Reproduce:
1.Install FC3 and create a non-user account when prompted.
2.After installation and reboot, create another account.
3.If you have FC3 already installed then just create an account with
useradd and compare the .bash_logout to the one in the root account.
  
Actual results:
Files are of different sizes.

Expected results:
Same file should exist in all accounts.

Additional info:

Comment 1 Tim Waugh 2005-01-13 14:58:05 UTC
The /etc/skel/.bash_logout file was altered in an update.


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