Nmap not working when implemented in crontab












1















I am trying to scan the network every day at a particular time(below example at 12:18) by using cronjobs and then output the IPs in a file. The command works perfectly but does not work if implemented in cronjobs. The following is implemented in /etc/crontab:




18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | grep 'Nmap scan' |
cut -d' ' -f5> HostList











share|improve this question



























    1















    I am trying to scan the network every day at a particular time(below example at 12:18) by using cronjobs and then output the IPs in a file. The command works perfectly but does not work if implemented in cronjobs. The following is implemented in /etc/crontab:




    18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | grep 'Nmap scan' |
    cut -d' ' -f5> HostList











    share|improve this question

























      1












      1








      1








      I am trying to scan the network every day at a particular time(below example at 12:18) by using cronjobs and then output the IPs in a file. The command works perfectly but does not work if implemented in cronjobs. The following is implemented in /etc/crontab:




      18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | grep 'Nmap scan' |
      cut -d' ' -f5> HostList











      share|improve this question














      I am trying to scan the network every day at a particular time(below example at 12:18) by using cronjobs and then output the IPs in a file. The command works perfectly but does not work if implemented in cronjobs. The following is implemented in /etc/crontab:




      18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | grep 'Nmap scan' |
      cut -d' ' -f5> HostList








      linux networking bash cron nmap






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 15 at 11:30









      Lgrech25Lgrech25

      61




      61






















          1 Answer
          1






          active

          oldest

          votes


















          0














          The most likely answer when a functional manual command doesn't behave properly when run as a cron job is because something is different when you run the command manually versus when cron spawns the job. That difference is most commonly that the PATH isn't the same, or the PWD (current directory) isn't the same.



          Solve those problems by specifying absolute paths on executables and filenames:



          18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | /bin/grep 'Nmap scan' | /usr/bin/cut -d' ' -f5 > /var/tmp/HostList


          Those paths are untested examples, chosen for illustrative purposes. You will need to verify the location of the executables and the desired location of your output file, and adjust the crontab entry accordingly.






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2fsuperuser.com%2fquestions%2f1406054%2fnmap-not-working-when-implemented-in-crontab%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The most likely answer when a functional manual command doesn't behave properly when run as a cron job is because something is different when you run the command manually versus when cron spawns the job. That difference is most commonly that the PATH isn't the same, or the PWD (current directory) isn't the same.



            Solve those problems by specifying absolute paths on executables and filenames:



            18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | /bin/grep 'Nmap scan' | /usr/bin/cut -d' ' -f5 > /var/tmp/HostList


            Those paths are untested examples, chosen for illustrative purposes. You will need to verify the location of the executables and the desired location of your output file, and adjust the crontab entry accordingly.






            share|improve this answer






























              0














              The most likely answer when a functional manual command doesn't behave properly when run as a cron job is because something is different when you run the command manually versus when cron spawns the job. That difference is most commonly that the PATH isn't the same, or the PWD (current directory) isn't the same.



              Solve those problems by specifying absolute paths on executables and filenames:



              18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | /bin/grep 'Nmap scan' | /usr/bin/cut -d' ' -f5 > /var/tmp/HostList


              Those paths are untested examples, chosen for illustrative purposes. You will need to verify the location of the executables and the desired location of your output file, and adjust the crontab entry accordingly.






              share|improve this answer




























                0












                0








                0







                The most likely answer when a functional manual command doesn't behave properly when run as a cron job is because something is different when you run the command manually versus when cron spawns the job. That difference is most commonly that the PATH isn't the same, or the PWD (current directory) isn't the same.



                Solve those problems by specifying absolute paths on executables and filenames:



                18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | /bin/grep 'Nmap scan' | /usr/bin/cut -d' ' -f5 > /var/tmp/HostList


                Those paths are untested examples, chosen for illustrative purposes. You will need to verify the location of the executables and the desired location of your output file, and adjust the crontab entry accordingly.






                share|improve this answer















                The most likely answer when a functional manual command doesn't behave properly when run as a cron job is because something is different when you run the command manually versus when cron spawns the job. That difference is most commonly that the PATH isn't the same, or the PWD (current directory) isn't the same.



                Solve those problems by specifying absolute paths on executables and filenames:



                18 12 * * * root /usr/bin/nmap -O 10.0.0.10-253 | /bin/grep 'Nmap scan' | /usr/bin/cut -d' ' -f5 > /var/tmp/HostList


                Those paths are untested examples, chosen for illustrative purposes. You will need to verify the location of the executables and the desired location of your output file, and adjust the crontab entry accordingly.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Feb 18 at 21:34

























                answered Feb 15 at 23:10









                Jim L.Jim L.

                42117




                42117






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1406054%2fnmap-not-working-when-implemented-in-crontab%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

                    How do I know what Microsoft account the skydrive app is syncing to?

                    When does type information flow backwards in C++?

                    Grease: Live!