On Fri, Apr 16, 2021 at 01:30:36PM +0200, Bálint Réczey wrote:
> Control: severity -1 wishlist
> Control: tags -1 confirmed upstream
>
> Hi Sam,
>
> Sam Morris ezt írta (időpont: 2021. ápr. 13., K, 19:45):
> >
> > On Tue, 2021-04-13 at 15:26 +0200, Chris Hofstaedtler wrote:
> > > This will then
Control: severity -1 wishlist
Control: tags -1 confirmed upstream
Hi Sam,
Sam Morris ezt írta (időpont: 2021. ápr. 13., K, 19:45):
>
> On Tue, 2021-04-13 at 15:26 +0200, Chris Hofstaedtler wrote:
> > This will then silently hide login failures from userids larger than
> > this ID? Given the orig
On Tue, 2021-04-13 at 15:26 +0200, Chris Hofstaedtler wrote:
> This will then silently hide login failures from userids larger than
> this ID? Given the original submitter has a user with uid 37940,
> why whould this not be logged?
>
> If they didn't want those uids to be used, maybe dont assi
* Sam Morris [210413 14:06]:
> So how about setting LASTLOG_UID_MAX to either 6 or 65536 depending
> on whether we want failed logins by 'nobody' to appear in lastlog(8) or
> not?
This will then silently hide login failures from userids larger than
this ID? Given the original submitter has a
Package: login
Followup-For: Bug #922945
X-Debbugs-Cc: s...@robots.org.uk
Control: affects -1 libpam-modules
Control: tag -1 patch
There is a hint as to what's going on in login.defs(5).
LASTLOG_UID_MAX (number)
Highest user ID number for which the lastlog entries should be
upda
Package: login
Version: 1:4.4-4.1
Somehow /var/log/lastlog grew to a 110 TByte sparse file:
# ls -al /var/log/lastlog
-rw-rw-r-- 1 root utmp 110784817228 Feb 22 08:37 /var/log/lastlog
# du -h /var/log/lastlog
88K /var/log/lastlog
This affects rsync performan
6 matches
Mail list logo
