Slackware :: Cron Job Not Working?
Nov 13, 2010I set up a job in my crontab file to clear the /tmp file on bootup with the following line:
Code:
@reboot rm-rf /tmp/*
My /tmp folder is not clearing. I've never used cron before;
I set up a job in my crontab file to clear the /tmp file on bootup with the following line:
Code:
@reboot rm-rf /tmp/*
My /tmp folder is not clearing. I've never used cron before;
Some of you are probably not going to believe this, but I've been using Linux for like four years and have never used cron for task scheduling before. Now I want to and I'm not sure how to do it. Could somebody link me to some good info? The results of a Google search were kinda confusing.
View 5 Replies View RelatedI'm going to rebuild a computer for a friend of mine. I'm going to install 12.2 in it and wanted to see if there was a way to install patches automatically from a cron. I don't think slackpkg can do such thing as a cron, correct? For anyone that set up a Slackware box for someone with little Linux knowledge, how did you handle the ability for the person to update the box?
View 13 Replies View RelatedI am trying to setup a cron job using crontab entry like this 6,16,26,36,46,56 * * * * /usr/bin/fetchmail -k>/dev/null 2>&1 But nothing is happening This is the first time I have attempted using cron as I have settup mutt for my email which is now working great but I would like to have the mail collected every 10 mins The file is saved as mailcron in my /home folder. When i run crontab -l its listed ok but no mail is appearing in mutt.
View 10 Replies View RelatedI was thinking of creating a little audio alarm clock with an mp3 and mpg123 to play a song from a cron job each day. How do you specify the time of day to execute a cron job?
View 4 Replies View RelatedI messed up when I chose my server for slackpkg updates, I chose one for Slackware13 rather then Slackware13 64. This caused some issues when I accepted the updates. I got a fair bit up and running again, but one thing that seems to be messed up is my cron.hourly scripts. I am not entirely sure what happened, but they are not running.
View 2 Replies View RelatedBy default, cron jobs are scheduled to run at 4:40 IIRC. I have my computer set to suspend after half an hour of inactivity so, except for some all-nighters, pretty much every day at that time my PC is suspended. What happens to the cron jobs? I don't suppose they run while the suspension is in effect. Do they get run when the computer wakes up or does cron wait until the next day at 4:40 to run the jobs?
View 5 Replies View RelatedAfter I create a cron job to shred some documents it seems to start and then immediately stop. What am I doing wrong? For instance, here is my cron:
#!/bin/sh
DISPLAY=:0.0
PATH = /usr/local/bin:/usr/bin:/usr/sbin:/bin:/sbin:
[code]....
I have a cron job to run every 15 minutes. The cron job is running per /var/log/cron. It lists the job every 15 minutes.
[Code]...
I do not see any errors. I also looked in /var/log/messages for any errors and it does not list any. I added a line to the script that is running to send an email to me to see if it is running or not. When I run the script from the command line, the script runs without error and I get an email. I have searched and can not find what it going on. Is there some where else errors might be? Could there be a permission issue? The cron job is not being added by the root user.
I have a ts3.desktop file in my /usr/share/applications folder that I want to run on system boot. I have typed the following commands which don't work
Code: Select allcrontab -e
Then in the editor, I typed the following line at the bottom of file. I also made the necessary carriage return after this line.
Code: Select all@reboot gtk-launch ts3 /usr/share/applications
Then I pressed ctrl+o to save it.
After I put these commands in, I did the following command to troubleshooting this issue, see below.
Code: Select all$ crontab -l
no crontab for server
$ps -ef | grep cron | grep -v grep
root 532 1 0 21:35 ? 00:00:00 /usr/sbin/cron -f
But after I reboot and nothing happens, the application doesn't start.
I'm trying to remotely schedule a shutdown using cron but I can't get it to work. I did setup the following 'sudo crontab -e'
Code:
For some reason doesn't this work, since I was able to login and get this output when using 'date'
Code:
I'm running cygwin 1.7 on a vanilla win2k3 r2 server. I've put together a simple crontab that I'll paste in her in a sec. The crontab entries call several shell scripts that do either scp's or rsync's from linux servers to this win2k3 box under cygwin.
The problem is that the scripts work and run fine from the commandline. Just not when called from the crontab. I'm running from the root equivalent administrator UID. The crontab log files are empty of errors.
crontab is:
Like I said, the scripts execute fine from the command line.
I run a Fedora 9 server at home, to host an "old school" MOO.To back up the database, I scheduled a cron job - and got some help with the script.I don't fiddle with stuff on the server much, because I don't really have a clue - leave well enough alone.But now I'm without backups. (I'd prefer to get this working, as it seemed pretty simple, and worked well for so long).
View 14 Replies View RelatedIt is little weird now that cron job is not working as i have set. I have set weekly job to send email but i am receiving multiple emails daily. Below is my code; # sends email every monday at 4:00 am 00 04 * * 1 /usr/bin/ruby /home/mbm/www/current/script/runner /home/mbm/www/current/app/models/add_to_delayed_job.rb -e production
00 -> Minutes
04 -> Hours (0-24)
1 -> Days / 0-6 / Sun - Sat
Sending email is fine but the time is not working so far as set.
I'm creating a script all worked fine in the command line. But not work in the cron. Below you could see the script
[Code]...
So far I found when I use corn following part not working, nothing goes to the processedfiles file. ls -l /var/lct/mou2/processed | grep $TODAY | awk '{print " " $8}' > /home/trans/mou/processedfiles ls -l /var/lct/mou2/processed | grep $YESTERDAY | awk '{print " " $8}' >> /home/trans/mou/processedfiles This work perfect in command line. Corn job and command line use by the same user.
I've read a lot on how to setup a task in crontab. I think I understand how to edit the file, but when I try to save the changes, it says "no crontab for xxx." Then it says that it cannot create a new crontab. I have ubuntu desktop 9 running as a webserver. I've read the details in these posts and it isn't helping.
[URL]
I make a script to automate burning backup files on dvd. It works fine if I start it from root user, but if I start it. From cronjob do noting. I try on growisofs the option -use-the-force-luke=force but nothing happens. I check the env of cron:
HOME=/root
LOGNAME=root
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
PWD=/root
SHELL=/bin/bash
SHLVL=1
XDG_SESSION_COOKIE=3e0d70f7b71074a0b1fff4bb4aa97d13-1281297181.926502-724038309
_=/usr/bin/env
and it seems ok i've got my script in /usr/local/bin and growisofs in /usr/bin
Code of my script below:
#!/bin/bash
bkup_path='/bkrepo/';
prefix='PAR*';
totdimfile=0
for FILE in $(/bin/ls -r $bkup_path$prefix)
do
dimfile=`/bin/ls -l $FILE | /usr/bin/awk -F " " '{print $5}' `
let "totdimfile += dimfile";
if [ "$totdimfile" -lt "4700000000" ]
then
NAMEFILE=`/bin/ls -l $FILE | /usr/bin/awk -F " " '{print $8}' `
ALLNAMEFILE="$ALLNAMEFILE $NAMEFILE";
fi
done
/usr/bin/growisofs -use-the-force-luke=force -Z /dev/scd0 -R -J $ALLNAMEFILE
/usr/bin/growisofs -M /dev/scd0=/dev/zero
/usr/bin/eject
end code of my script
How to schedule a job using cron that shouldn't run between working hrs 9am-5pm, while run in non working hrs every hour, every day of the month, month & week.I tried the following way, not sure I can use logical not operator(!).
View 3 Replies View RelatedGot a small problem, I'm trying to schedule a script to run every Thursday at midday and the scheduled tasks application on Ubuntu doesn't seem to work. The script is fine when I run it from a terminal.I have zero experience using cron at the command line, can anyone tell me what I should do?
View 2 Replies View RelatedI am new to Linux and have done an install of Moodle 1.9.8 on Linux OpenSuse 11.0
I have created my cron via the terminal (crontab -e) root crontab - see below:
When going to /var/log/messages my cron entries appear as they should but my backup does not run and every morning when I go to the Notifications tab it tells me my crom maintenance script has not run in 24hours.
I would also like to get this in a log file and emailed to me.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# m h dom mon dow user command
[code]...
The back.sh script is being run as user basil, whcih means that when it comes to copying the backup file to the target location you do not have the correct permissions to access the contents of the directory (it is rwx by root only).So, what do we do? Hoping it is ONLY the directory permissions which are fouling things up we have a range of options which, in not particular order of 'good', include:
a) change ownership/permission on target directory.
b) have the back.sh script run by the root user
c) set up sudo to permit the file copy to be done by root
d) use setuid on the back.sh to have it run, effectively, as root
A lot of the answer will depend upon what else the Dropbox directory is for. If it's JUST for your backups for this then I'd be inclined to:
Code:
chown basil /root/Dropbox
chmod g+rwx /root/Dropbox
which will permit the basil user full access and thus allow the file operations being done and give root access via the group permissions (not that the root user really needs this).Also, I'd be inclined to:
Code:
chown basil /home/xxxx/moo3/bin/back.sh
chmod u=rwx,g=rx,o= /home/xxxx/moo3/bin/back.sh
which will make things 'look' better, it just reinforces the point that the script is run (and owned) by the basil user.
Have a headless server running Lucid 64 bit. Everything is working great except for a couple of Cron jos I'm trying to have run at boot.
My user crontab looks like this:
# m h dom mon dow command
01 * * * * /home/ceallred/Scripts/SambaBkup.sh
@reboot /usr/bin/SpiderOak --headless &The SambaBkup script works like clockwork...
The SpiderOak job doesn't start. It works if I type the command in manually.
syslog only shows:Jul 13 22:45:33 RavenWing cron[1010]: (CRON) INFO (pidfile fd = 3)
Jul 13 22:45:33 RavenWing cron[1022]: (CRON) STARTUP (fork ok)
Jul 13 22:45:33 RavenWing cron[1022]: (CRON) INFO (Running @reboot jobs)
Jul 13 22:45:33 RavenWing CRON[1048]: (ceallred) CMD (/usr/bin/SpiderOak --headless &)Yet ps -A doesn't show a running SpiderOak process. It shows after starting manually.
I am running a series of operations on executable matlab scripts which are connecting python and fortran scripts. I schedule the executables in cron. The problem:
- My original matlab scripts work perfectly.
- My executables work perfectly if I run them from the terminal. - Using the gui scheduled tasks and running the scripts once from a button, everything also works fine.
- But when I leave the scheduled tasks run on their own, I get an error! The error can be that the script hangs in general (I have some text logs exported every step to track the progress), or I get an error which never appears when I run the script with any of the other mentioned ways.
- I tried both cron command prompt or the GUI scheduled tasks
- I am running on Ubuntu 64 bit
I am attempting to schedule a task to run every hour. I have altered the crontabs for my account but the the task still won't run on the hour.
View 1 Replies View RelatedI have two servers. One of them has a svn server running and another hosting projects.
I have a daily cronjob updating the projects -- ie running svn update, rebuild etc.
Now, my cronjob on the remote server works.
However, a similar cronjob running on the local server for local projects (ie the same server as svn) is instead displaying a "svn: not working copy".
I double checked the paths, permissions and user info and if the script is launched manually, it works fine.
Deploying the same thing remotely works.
I even tried using file:/// (suggested here http://www.hightekhosting.com.au/myaccount/knowledgebase/90/Using-SubversionorSVN-on-cPanel-Servers.html) but still nothing.
I installed an LAMP Server on 10.10. Additionally a simple Sambaserver and a VPN is integrated. Since 3 days I look at some strange behaviour:
Code: sudo init 6 does not take effect. Nothing happens. Code: sudo reboot is working, but all seems to be so ropy. It takes a significant while, before ssh-session is finally terminated. After the system comes up again, the vpn-client gets not the same IP-address by DHCP-server, but the next following of dhcp-range. That is strange, because no other dhcp-client is busy. After a second reboot I get the correct first IP-address of the dhcp-range. That is reproducible.
cron is not working any more. None of my jobs is being triggered. Nothing is logged in /var/log/syslog any more. Services (apache2, mysql, smbd) are not running at the start. I have to run them up manually. Seems like init is somehow smashed? What is your guess? What futher information do I have to provide for analysis?
Can anyone tell me how i change the default domain name for cron?everything i cron runs it emails from and to user@com.com
this leaves me with a massive list of failed mails in postfix.i have mailto on my main crontab but i cant do it on all of them.
I have added some executable scripts to /etc/cron.daily but don't get the stdout/stderr output from them as mail (or anywhere else I have found). At least one of them is running (because I can see that it has added a file to the disk).
The peculiar thing is that I do get the output from /etc/cron.daily/0logwatch (part of the logwatch package) as an email each day.
The MAILTO line in /etc/crontab is "MAILTO=root" (unchanged from default). Same for /etc/anacrontab.
I do have an alias at the end of /etc/aliases which redirects root's mail to my own account, but this alias works fine for mail I send manually. (It also appears to work fine for the output from the file /etc/cron.daily/0logwatch.)
It seems that cron is not upgrading my Ubuntu 8.04 LTS Server, no GUI installed. I changed /etc/crontab and watched apt running:
Code:
ps -A | grep apt
showed it for a long time,
Code:
sudo tcpdump tcp
showed communication with canonical sites,
but:
Code:
top
did not show any apt using CPU
[code].....