Re: Lsuser Not Reporting Correctly

terry.german_at_PHONES4U.CO.UK
Date: 10/26/04

  • Next message: Mills, John T (9814): "Re: changing uptime"
    Date:         Tue, 26 Oct 2004 14:33:19 +0100
    To: aix-l@Princeton.EDU
    
    
    

    My solution would be to clear out lastlog via >lastlog and let it recreate
    itself and re-index.

    -----Original Message-----
    From: Andrew Townsend [mailto:Andrew.Townsend@BISYS.COM]
    Sent: 26 October 2004 14:03
    To: aix-l@Princeton.EDU
    Subject: Re: Lsuser Not Reporting Correctly

    So what's your solution?

                          terry.german@PHON
                          ES4U.CO.UK To: aix-l@Princeton.EDU
                          Sent by: IBM AIX cc:
                          Discussion List Subject: Re: Lsuser Not
    Reporting Correctly
                          <aix-l@Princeton.
                          EDU>

                          10/26/2004 08:48
                          AM
                          Please respond to
                          IBM AIX
                          Discussion List

    All,

    Thanks for the help but what I think it is... is this

    I ran the mkpasswd command (about 6 months ago) which puts indexes on the
    passwd and lastlog file.. now the lastlog index is 5 months out of data and
    when I try and view the lastlog file I get a "out of memory" error, so what
    I think is wrong is the lastlog file is too large (23MB) and when a new
    user is created as the system can't properly read the lastlog file it can't
    put in the correct information, or something like that.

    Thanks
          -----Original Message-----
          From: Toalston, Michael [mailto:MToalston@GEICO.COM]
          Sent: 26 October 2004 13:18
          To: aix-l@Princeton.EDU
          Subject: Re: Lsuser Not Reporting Correctly

          Are you running the lsuser command from root? Results are different
          running as normal user on my 5.1 boxes.

          Michael Toalston
          Unix System Admin
          Geico Direct

          From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf
          Of terry.german@PHONES4U.CO.UK
          Sent: Tuesday, October 26, 2004 6:41 AM
          To: aix-l@Princeton.EDU
          Subject: Lsuser Not Reporting Correctly

          Before acting on this e-mail or opening any attachments you are
          advised to read
          The Caudwell Holdings group of companies' disclaimer at the end of
          this e-mail.
          =======================================================

          Guru's,

          It would be great if any of you can help me out here..

          I am running the lsuser command on different ids and the results are
          not reporting any iformation after the "roles=" part. It seems to be
          either a flag isn't turned on or something else. Any new id that is
          created and logged in doesn't report all the information .i.e
          time_last_login=1098439418 etc even if root creates the id the same
          happens.

          The server is a M80, the OS is AIX 4.3.3.

          Thanks in advance

          Terry German
          AIX System Administrator
          IBM Certified Specialist - AIX
          Line Of Business Team
          Phones 4u Limited
          Phones4u House
          Brymbo Road
          Lymedale Business Park
          Newcastle Under Lyme
          ST5 9HI.
          [E] terry.german@phones4u.co.uk
          <mailto:terry.german@phones4u.co.uk>
          [T] +44 (0)1782 677813
          [M] +44 (0)7748908609
          [F] +44 (0)1782 677809
          [W] http://www.phones4u.co.uk

          For the very latest mobile phone offers visit Phones4u.co.uk
          =======================================================
          Confidentiality Notice
          This e-mail is confidential and intended for the use of the named
          recipient only. If you are not the intended recipient please notify
          us by telephone immediately on +44(0)1782 600600 or return it to us
          by e-mail. Please then delete it from your system and note that any
          use, dissemination, forwarding, printing or copying is strictly
          prohibited.

          Any views or opinions are solely those of the author and do not
          necessarily represent those of The Caudwell Holdings group of
          companies.

          Encryptions and Viruses
          Please note that this e-mail and any attachments have not been
          encrypted. They may therefore be liable to be compromised. Please
          also note that it is your responsibility to scan this e-mail and any
          attachments for viruses. We do not, to the extent permitted by law,
          accept any liability (whether in contract, negligence or otherwise)
          for any virus infection and/or external compromise of security and/or

          confidentiality in relation to transmissions sent by e-mail.

          Monitoring
          Activity and use of The Caudwell Holdings group of companies' systems
          is monitored to secure its effective use and operation and for other
          lawful business purposes. Communications using these systems will
          also be monitored and may be recorded to secure effective use and
          operation and for other lawful business purposes.

          ====================

          This email/fax message is for the sole use of the intended
          recipient(s) and may contain confidential and privileged information.
          Any unauthorized review, use, disclosure or distribution of this
          email/fax is prohibited. If you are not the intended recipient,
          please destroy all paper and electronic copies of the original
          message.

    This email is confidential and intended solely for the use of the
    individual or entity to whom it is addressed. If you have received this
    email in error please notify the system manager at mailadmin@bisys.com and
    delete the email immediately.

    <! For the very latest mobile phone offers visit >
    <! www.phones4u.co.uk >

    <font face="arial" color=#f00000 size=3>For the very latest mobile phone offers visit </font>Phones4u.co.uk</font>
    =======================================================
    Confidentiality Notice
    This e-mail is confidential and intended for the use of the named recipient only. If you are not the intended recipient please notify us by telephone immediately on +44(0)1782 600600 or return it to us by e-mail. Please then delete it from your system and note that any use, dissemination, forwarding, printing or copying is strictly prohibited.

    Any views or opinions are solely those of the author and do not necessarily represent those of The Caudwell Holdings group of companies.

    Encryptions and Viruses
    Please note that this e-mail and any attachments have not been encrypted. They may therefore be liable to be compromised. Please also note that it is your responsibility to scan this e-mail and any attachments for viruses. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or
    confidentiality in relation to transmissions sent by e-mail.

    Monitoring
    Activity and use of The Caudwell Holdings group of companies' systems is monitored to secure its effective use and operation and for other lawful business purposes. Communications using these systems will also be monitored and may be recorded to secure effective use and operation and for other lawful business purposes.


  • Next message: Mills, John T (9814): "Re: changing uptime"

    Relevant Pages

    • Re: OpenSSH, AIX and lastlog
      ... >OpenSSH 3.4 is not making entries of any kind in the lastlog file. ... IBM changed the format of the wtmp entries between 4.x and 5.x for some ... Were your binaries compiled on AIX 4? ...
      (comp.security.ssh)
    • Re: Possible compromise ?
      ... The only place, where those connections are mentioned, is the lastlog file. ... Subject: Possible compromise? ... >> Unreadable chaos, bad dates. ...
      (FreeBSD-Security)