17 comment

  1. thanks a lot vivek.i din’t expect this much fast reply.But unfortunately when i execute,
    $ last | grep $(date ‘+%a %b %d’)
    i couldn’t get anything.Please help

  2. My bad…I forgot to include double quote …

    59 11 * * * last | grep "$(date '+%a %b %d')" > /tmp/users.out ; mail -s “Users Logged"

    Also you may wanna try out:

    last -t yyyymmddhhmmss

    HTH

    1. In order to track who rebooted a linux machine, I would:
      – disable root logins; many users sharing root is bad
      – create a list of sudoers, so only people listed there could shutdown / reboot / halt
      – /var/log/messages would contain traces of who ran sudo shutdown -r now or such

  3. wtmp is rotated by the system, so the last solution will stop working. I believe the most reliable solution is:

    date -d "`cut -f1 -d. /proc/uptime` seconds ago"
    1. The uptime idea from Sam is nice but really that just returns the uptime (same as the uptime command) in date format.

  4. Is there any way to check if the system is currently rebooting? Or shutting down

    I made a cron job that will reboot the server when a specific file exists (deleting that file too of course)
    So that I can use php to make it and signal a reboot when needed
    When cron job fires, the few seconds of shutting down will trigger database connection error
    So I want to know if there is any standard way of knowing the system is rebooting aside from making another file that existence signals “server is rebooting” (which I don’t know how to delete when server is back up anyway)

  5. Hi!

    tuptime is an other command that you can use for get this information. I found it after trying all the typical commands. I think that it covers better this subject that the solutions proposed here

    An example, with enumerate option:

    # tuptime -e
    Startup: 1 at 08:25:03 AM 08/28/2015
    Uptime: 14 minutes and 38 seconds
    Shutdown: OK at 08:39:41 AM 08/28/2015

    Downtime: 6 seconds

    Startup: 2 at 08:39:48 AM 08/28/2015
    Uptime: 10 minutes and 36 seconds
    Shutdown: BAD at 08:50:24 AM 08/28/2015

    Downtime: 7 minutes and 16 seconds

    Startup: 3 at 08:57:41 AM 08/28/2015
    Uptime: 10 minutes and 22 seconds
    Shutdown: BAD at 09:08:03 AM 08/28/2015

    Downtime: 6 minutes and 12 seconds

    Startup: 4 at 09:14:16 AM 08/28/2015
    Uptime: 1 minutes and 7 seconds
    Shutdown: BAD at 09:15:23 AM 08/28/2015

    Downtime: 2 minutes and 35 seconds

    Startup: 5 at 09:17:59 AM 08/28/2015
    Uptime: 1 minutes and 15 seconds
    Shutdown: BAD at 09:19:14 AM 08/28/2015

    Downtime: 8 hours, 32 minutes and 8 seconds

    Startup: 6 at 05:51:23 PM 08/28/2015
    Uptime: 2 days, 16 hours, 53 minutes and 19 seconds
    Shutdown: BAD at 10:44:42 AM 08/31/2015

    Downtime: 22 hours, 13 minutes and 17 seconds

    Startup: 7 at 08:58:00 AM 09/01/2015
    Uptime: 7 hours, 23 minutes and 51 seconds
    Shutdown: OK at 04:21:51 PM 09/01/2015

    Downtime: 11 seconds

    Startup: 8 at 04:22:03 PM 09/01/2015
    Uptime: 41 seconds
    Shutdown: OK at 04:22:44 PM 09/01/2015

    Downtime: 6 seconds

    Startup: 9 at 04:22:51 PM 09/01/2015
    Uptime: 4 minutes and 11 seconds
    Shutdown: OK at 04:27:02 PM 09/01/2015

    Downtime: 5 seconds

    Startup: 10 at 04:27:08 PM 09/01/2015
    Uptime: 1 days, 16 hours, 14 minutes and 32 seconds

    System startups: 10 since 08:25:03 AM 08/28/2015
    System shutdowns: 4 ok – 5 bad
    Average uptime: 11 hours, 19 minutes and 27 seconds
    Average downtime: 3 hours, 6 minutes and 12 seconds
    Current uptime: 1 days, 16 hours, 14 minutes and 32 seconds since 04:27:08 PM 09/01/2015
    Uptime rate: 78.49 %
    Downtime rate: 21.51 %
    System uptime: 4 days, 17 hours, 14 minutes and 35 seconds
    System downtime: 1 days, 7 hours, 2 minutes and 1 seconds
    System life: 6 days, 0 hours, 16 minutes and 37 seconds

    The repository is located at: https://github.com/rfrail3/tuptime

    Regards,

Comments are closed.