Why has my 'last' command suddenly stopped working?

Why has my 'last' command suddenly stopped working?

Post by Troy Kena » Thu, 23 Mar 1995 09:41:30

I'm running Solaris 2.3 (patched like a quilt). Our machine (SS20/612)
a couple of weeks ago and ever since then the 'last' command only shows
info up to the date of the crash. The file in /var/adm
are still being updated - judging by file-size and date - yet 'last' just
doesn't work.

Any ideas...?



1. Why doesn't echo "text" 'command' "more text" work?

                 ^                                        ^
Wrong quotes, should be -
   echo "You have" `grep Subject: /usr/spool/mail/me | wc -l` "messages."
or -
   echo "You have `grep Subject: /usr/spool/mail/me | wc -l` messages."

But, another problem is, if you've no mail, /usr/spool/mail/me does not
exist, leading grep to say:
   grep: can't open /usr/spool/mail/me
Wc will still report 0.

You might try -
   sh -c 'echo "You have `grep 2>/dev/null Subject: /usr/spool/mail/me | wc -l` messages."'

Hope this helps.

2. crosstalk

3. getting ~/.xsession working on Redhat/GNOME combo

4. 'last' command doesn't show complete login times

5. who cares for broken arch/mips/galileo-boards/ev64120/compressed ?

6. Sun's 'last' command

7. PCMCIA 10B2 ?

8. The 'last' command doesn't record users logout

9. why would 'cp' or 'ls -al' command hangs on Solaris 2.7 ?

10. having problems with 'find' command

11. Help: problems with 'w', 'who' and 'last'

12. the 'last' command