Friday, May 10, 2024
 Popular · Latest · Hot · Upcoming
2
rated 0 times [  2] [ 0]  / answers: 1 / hits: 852  / 1 Year ago, sun, march 5, 2023, 2:51:19

As a root I run three dd processes in the background


dd if=/dev/urandom of=/dev/null &
dd if=/dev/urandom of=/dev/null &
dd if=/dev/urandom of=/dev/null &

As a root I edit a crontab and put a job to kill all dd processes that were run by root every minute


crontab -e 

* * * * * pkill -u root dd

But when I use top to monitor processes the dd processes don't get killed. Why ?


Messages from /var/log/syslog :


Dec  9 12:33:01 champion CRON[3395]: Authentication failure
Dec 9 12:33:29 champion crontab[3383]: (root) END EDIT (root)
Dec 9 12:34:01 champion cron[1432]: Authentication failure
Dec 9 12:34:01 champion CRON[3398]: Authentication failure

Tried these suggestions but it didn't help :



  1. Invoke the crontab with :


    crontab -e -u root



  2. Make sure that you have an empty line at the end of the cronjob file, meaning that every line ends with a newline.




More From » cron

 Answers
1

Based on the following diagnostic output from pwck -r:


no matching password file entry in /etc/shadow add user 'root' in /etc/shadow?

you can see that the problem is the same as described here:



You can fix it by running pwck again, this time in read-write mode


sudo pwck

and accepting the suggested action to add the appropriate shadow file entry for user root.


[#2256] Monday, March 6, 2023, 1 Year  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
mugustered

Total Points: 193
Total Questions: 123
Total Answers: 108

Location: Bermuda
Member since Wed, Mar 22, 2023
1 Year ago
mugustered questions
Sat, Nov 19, 22, 07:03, 2 Years ago
Sun, May 29, 22, 11:53, 2 Years ago
Fri, Dec 23, 22, 15:02, 1 Year ago
;