SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Is this command in the crontab of a user or root. If it's a user's crontab then there may be a problem as the command will be ran as that user and maybe failing. Don't know why the other machines are working OK though. Personally I'd always put such stuff in /etc/rc.d/rc.local_shutdown anyway. I'd start by looking at permissions and ownership of stuff in /tmp/ and who owns the crontab on all machines.
Is this command in the crontab of a user or root. If it's a user's crontab then there may be a problem as the command will be ran as that user and maybe failing. Don't know why the other machines are working OK though. Personally I'd always put such stuff in /etc/rc.d/rc.local_shutdown anyway. I'd start by looking at permissions and ownership of stuff in /tmp/ and who owns the crontab on all machines.
Someone posted a similar question here once and if I recall correctly, there was no space between the rm and the -rf. So maybe check your syntax to make sure there's no typo?
Make sure crond is running (`ps aux | grep [c]rond` should do the trick), make sure the command is listed properly in the output of `crontab -l`, try adding/removing a blank line at the end of the file, and try using the explicit path to /bin/rm. Also note that your command will not remove dot files in /tmp.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.