[SOLVED] Nmap not working when implemented in crontab
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It worked Guys Thanks a lot. After changing the directory and implementing everything in the sudo crontab -e. It updated 2/3 minutes after because of the namp process. Sorry for bothering you a lot
crond will detect when /etc/crontab has changed and reload the file so there is no need to restart the service.
I agree with joe_2000 that it should work and it does from my debian system. The changes I made were to add a space between -d and
' ' in the cut command and add an absolute path to the output file.
It worked Guys Thanks a lot. After changing the directory and implementing everything in the sudo crontab -e. It updated 2/3 minutes after because of the namp process. Sorry for bothering you a lot
Cool. So in summary, the original problem was that the output file ended up in some other location than you expected? Probably /root ?
Either way: It's good advice from TBOne to use crontab -e as this will also do syntax checking on your crontab entries and complain if the syntax is wrong.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.