Bug 57054 - Huge /var/log/lastlog due to high nfsnobody UID
Summary: Huge /var/log/lastlog due to high nfsnobody UID
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: nfs-utils   
(Show other bugs)
Version: 7.2
Hardware: All Linux
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2001-12-03 21:22 UTC by Jim Richardson
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-12-03 21:24:03 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 Jim Richardson 2001-12-03 21:22:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)

Description of problem:
the lastlog file appears to be a flat file indexed by UID. Creating the 
nfsnobody account at a high value effectively cause nfsnobody UID - 
highest normal UID empty records to be insterted into the lastlog file.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install latest nfs-utils*.rpm


Actual Results:  Size of lastlog on all systems jumped to nearly 2 MEG

Additional info:

Comment 1 Pete Zaitcev 2002-08-20 00:05:46 UTC
This is normal. If you did not copy it, the file is going to
be holey - it uses very little space.

[zaitcev@niphredil linux-2.5.30-sparc]$ ls -l /var/log/lastlog
-rw-r--r--    1 root     root     19136220 Aug 19 15:50 /var/log/lastlog
[zaitcev@niphredil linux-2.5.30-sparc]$ du -ks /var/log/lastlog
[zaitcev@niphredil linux-2.5.30-sparc]$ 

I do not think anything can easily be done about it.
The default value of nfsnobody is selected to be compatible
with Solaris. I suppose someone can change lastlog to be
a db3 file, but that's not that trivial (consider locking,
and it adds one more dependancy for core utilities...)

Please poke Support if it causes any particular problems
besides the psychological shock from the ls -l output.

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