Script to see if user has logged off












1















I have created this program to see if a user is logged on and it checks every minute.



if [ "$#" -ne 1 ]
then
echo "Usage: mon user"
exit 1
fi
user="$1"
until who | grep "^$user " > /dev/null
do
sleep 60
done

echo "$user has logged on"


But my question is how can I modify this program to see if a user has logged off instead of logging in?



Thanks for any help provided! Much appreciated.










share|improve this question
















bumped to the homepage by Community 21 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1





    You could simply change until to while, but I do not think this is the most efficient or elegant method to be notified of user login activity.

    – jw013
    Nov 13 '14 at 0:51











  • Couldn't just use -v with the grep to and print out that user is not logged in? Of course, it won't tell you whether the user had logged in and then logged out, but would just tell you whether the user is logged in at the moment.

    – Sree
    Nov 13 '14 at 4:52
















1















I have created this program to see if a user is logged on and it checks every minute.



if [ "$#" -ne 1 ]
then
echo "Usage: mon user"
exit 1
fi
user="$1"
until who | grep "^$user " > /dev/null
do
sleep 60
done

echo "$user has logged on"


But my question is how can I modify this program to see if a user has logged off instead of logging in?



Thanks for any help provided! Much appreciated.










share|improve this question
















bumped to the homepage by Community 21 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1





    You could simply change until to while, but I do not think this is the most efficient or elegant method to be notified of user login activity.

    – jw013
    Nov 13 '14 at 0:51











  • Couldn't just use -v with the grep to and print out that user is not logged in? Of course, it won't tell you whether the user had logged in and then logged out, but would just tell you whether the user is logged in at the moment.

    – Sree
    Nov 13 '14 at 4:52














1












1








1








I have created this program to see if a user is logged on and it checks every minute.



if [ "$#" -ne 1 ]
then
echo "Usage: mon user"
exit 1
fi
user="$1"
until who | grep "^$user " > /dev/null
do
sleep 60
done

echo "$user has logged on"


But my question is how can I modify this program to see if a user has logged off instead of logging in?



Thanks for any help provided! Much appreciated.










share|improve this question
















I have created this program to see if a user is logged on and it checks every minute.



if [ "$#" -ne 1 ]
then
echo "Usage: mon user"
exit 1
fi
user="$1"
until who | grep "^$user " > /dev/null
do
sleep 60
done

echo "$user has logged on"


But my question is how can I modify this program to see if a user has logged off instead of logging in?



Thanks for any help provided! Much appreciated.







bash logs users administration






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 13 '14 at 4:25









jasonwryan

49.9k14134188




49.9k14134188










asked Nov 13 '14 at 0:27









AphicisAphicis

62




62





bumped to the homepage by Community 21 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 21 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 1





    You could simply change until to while, but I do not think this is the most efficient or elegant method to be notified of user login activity.

    – jw013
    Nov 13 '14 at 0:51











  • Couldn't just use -v with the grep to and print out that user is not logged in? Of course, it won't tell you whether the user had logged in and then logged out, but would just tell you whether the user is logged in at the moment.

    – Sree
    Nov 13 '14 at 4:52














  • 1





    You could simply change until to while, but I do not think this is the most efficient or elegant method to be notified of user login activity.

    – jw013
    Nov 13 '14 at 0:51











  • Couldn't just use -v with the grep to and print out that user is not logged in? Of course, it won't tell you whether the user had logged in and then logged out, but would just tell you whether the user is logged in at the moment.

    – Sree
    Nov 13 '14 at 4:52








1




1





You could simply change until to while, but I do not think this is the most efficient or elegant method to be notified of user login activity.

– jw013
Nov 13 '14 at 0:51





You could simply change until to while, but I do not think this is the most efficient or elegant method to be notified of user login activity.

– jw013
Nov 13 '14 at 0:51













Couldn't just use -v with the grep to and print out that user is not logged in? Of course, it won't tell you whether the user had logged in and then logged out, but would just tell you whether the user is logged in at the moment.

– Sree
Nov 13 '14 at 4:52





Couldn't just use -v with the grep to and print out that user is not logged in? Of course, it won't tell you whether the user had logged in and then logged out, but would just tell you whether the user is logged in at the moment.

– Sree
Nov 13 '14 at 4:52










2 Answers
2






active

oldest

votes


















0














You can filter the secure log file (assuming you are just checking for remote login). The secure log file tells you when a user logs in and logs out. Also check the lastlog command as well as the wtmp and utmp files. They'll contain historical data for user logins.






share|improve this answer
























  • /var/log/secure may not be set up in all distros. I think systemd has thrown away /var/log in favor of journalctl. I like the idea of using who w better as this will include those who are logged in non-remotely.

    – SailorCire
    Nov 13 '14 at 15:13





















0














Try this.



#!/bin/bash

[ "$#" -ne 1 ] && {
echo "Usage: $(basename $0) user"
exit 1
}

user="$1"
grep "^$user:" /etc/passwd > /dev/null || {
echo "There's no user called $user in this system."
exit 2
}

who | grep "^$user " > /dev/null && sleep 60

echo "$user has logged out"





share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f167659%2fscript-to-see-if-user-has-logged-off%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    You can filter the secure log file (assuming you are just checking for remote login). The secure log file tells you when a user logs in and logs out. Also check the lastlog command as well as the wtmp and utmp files. They'll contain historical data for user logins.






    share|improve this answer
























    • /var/log/secure may not be set up in all distros. I think systemd has thrown away /var/log in favor of journalctl. I like the idea of using who w better as this will include those who are logged in non-remotely.

      – SailorCire
      Nov 13 '14 at 15:13


















    0














    You can filter the secure log file (assuming you are just checking for remote login). The secure log file tells you when a user logs in and logs out. Also check the lastlog command as well as the wtmp and utmp files. They'll contain historical data for user logins.






    share|improve this answer
























    • /var/log/secure may not be set up in all distros. I think systemd has thrown away /var/log in favor of journalctl. I like the idea of using who w better as this will include those who are logged in non-remotely.

      – SailorCire
      Nov 13 '14 at 15:13
















    0












    0








    0







    You can filter the secure log file (assuming you are just checking for remote login). The secure log file tells you when a user logs in and logs out. Also check the lastlog command as well as the wtmp and utmp files. They'll contain historical data for user logins.






    share|improve this answer













    You can filter the secure log file (assuming you are just checking for remote login). The secure log file tells you when a user logs in and logs out. Also check the lastlog command as well as the wtmp and utmp files. They'll contain historical data for user logins.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 13 '14 at 2:37









    Tito ValentinTito Valentin

    262




    262













    • /var/log/secure may not be set up in all distros. I think systemd has thrown away /var/log in favor of journalctl. I like the idea of using who w better as this will include those who are logged in non-remotely.

      – SailorCire
      Nov 13 '14 at 15:13





















    • /var/log/secure may not be set up in all distros. I think systemd has thrown away /var/log in favor of journalctl. I like the idea of using who w better as this will include those who are logged in non-remotely.

      – SailorCire
      Nov 13 '14 at 15:13



















    /var/log/secure may not be set up in all distros. I think systemd has thrown away /var/log in favor of journalctl. I like the idea of using who w better as this will include those who are logged in non-remotely.

    – SailorCire
    Nov 13 '14 at 15:13







    /var/log/secure may not be set up in all distros. I think systemd has thrown away /var/log in favor of journalctl. I like the idea of using who w better as this will include those who are logged in non-remotely.

    – SailorCire
    Nov 13 '14 at 15:13















    0














    Try this.



    #!/bin/bash

    [ "$#" -ne 1 ] && {
    echo "Usage: $(basename $0) user"
    exit 1
    }

    user="$1"
    grep "^$user:" /etc/passwd > /dev/null || {
    echo "There's no user called $user in this system."
    exit 2
    }

    who | grep "^$user " > /dev/null && sleep 60

    echo "$user has logged out"





    share|improve this answer




























      0














      Try this.



      #!/bin/bash

      [ "$#" -ne 1 ] && {
      echo "Usage: $(basename $0) user"
      exit 1
      }

      user="$1"
      grep "^$user:" /etc/passwd > /dev/null || {
      echo "There's no user called $user in this system."
      exit 2
      }

      who | grep "^$user " > /dev/null && sleep 60

      echo "$user has logged out"





      share|improve this answer


























        0












        0








        0







        Try this.



        #!/bin/bash

        [ "$#" -ne 1 ] && {
        echo "Usage: $(basename $0) user"
        exit 1
        }

        user="$1"
        grep "^$user:" /etc/passwd > /dev/null || {
        echo "There's no user called $user in this system."
        exit 2
        }

        who | grep "^$user " > /dev/null && sleep 60

        echo "$user has logged out"





        share|improve this answer













        Try this.



        #!/bin/bash

        [ "$#" -ne 1 ] && {
        echo "Usage: $(basename $0) user"
        exit 1
        }

        user="$1"
        grep "^$user:" /etc/passwd > /dev/null || {
        echo "There's no user called $user in this system."
        exit 2
        }

        who | grep "^$user " > /dev/null && sleep 60

        echo "$user has logged out"






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 30 '16 at 14:58









        TomaszTomasz

        9,52652965




        9,52652965






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f167659%2fscript-to-see-if-user-has-logged-off%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            CARDNET

            Boot-repair Failure: Unable to locate package grub-common:i386

            濃尾地震