Red Hat Bugzilla – Bug 57054
Huge /var/log/lastlog due to high nfsnobody UID
Last modified: 2007-04-18 12:38:33 EDT
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):
Steps to Reproduce:
1. install latest nfs-utils*.rpm
Actual Results: Size of lastlog on all systems jumped to nearly 2 MEG
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
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.