Util-Linux package development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: "Mantas Mikulėnas" <grawity@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: lslogins --user-accs
Date: Wed, 15 Jul 2015 16:23:44 +0200	[thread overview]
Message-ID: <20150715142344.GF31997@ws.net.home> (raw)
In-Reply-To: <mnesfe$veu$1@ger.gmane.org>

On Tue, Jul 07, 2015 at 12:37:49AM +0300, Mantas Mikulėnas wrote:
> Trying out `lslogins`, noticed two problems (?) with the --user-accs option:
> 
> 1) The manpage documents --user-accs[=threshold] to override the
> "hardcoded" minimum of 1000, but the code doesn't actually /accept/ a
> parameter (it reads the actual threshold from login.defs).
> 
> 2) While not documented, --user-accs also applies the /maximum/ uid
> limit. I noticed this on a system that has "UID_MAX 19999" because
> LDAP-based accounts start at 20000, which means `lslogins -u` will show
> local users but not LDAP ones.
 
For now I have fixed the man page and removed [=threshold] and added
hint about uids ranges specified by /etc/login.defs.

Maybe the ideal solution would be to add optional parameter

    --user-accs[=min:max]
    --system-accs[=min:max]


> Also the "Last logs:" output seems to have ^A / 0x01 in random places:
> 
>   00:35:14 krenew<^A>\x01[1295]: renewing credentials
> 
> On another system:
> 
>   Feb07/00:05 sshd[3009657]: Received disconnect from 78.60.211.195: 11:
> disconnected by user<^A>

Hmm... we read this from systemd journal by sd_journal_get_data() and
print it without any change.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      reply	other threads:[~2015-07-15 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 21:37 lslogins --user-accs Mantas Mikulėnas
2015-07-15 14:23 ` Karel Zak [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150715142344.GF31997@ws.net.home \
    --to=kzak@redhat.com \
    --cc=grawity@gmail.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox