Tag Info

New answers tagged

0

I do not believe cron itself is the correct method but Wireshark has native support for doing a capture on the USB interfaces. From the link: Linux To dump USB traffic on Linux, you need the usbmon module, which has existed since Linux 2.6.11. Information on that module is available in /usr/src/linux/Documentation/usb/usbmon.txt in the Linux source ...


0

I finally found a way to get around this issue. Maybe this solution will help others as well. Regarding the missing file /etc/cron.daily/apt: The file is part of the apt package. Thus, I downloaded the package via apt-get download apt, extracted it and manually copied the file named apt to the said location. I do not know why this file has not been copied ...


0

I have a file called 10periodic, which I haven't created myself; it is identical to the on in the linked question. I also have a file /etc/cron.daily/apt which is much longer, but looks much the same as the one in the link. Either copy that one over to your installation, or try installing cron-apt.


0

Solution Here is the problem : There is a awstats jobs setup on /etc/cron.d which is run with www-data. This one is causing the problem cause www-data doesn't have access to /var/log/apache2 First you need to : chmod o+rx /var/log/apache2 Next you need to change on /etc/logrotate.d/apache2 create 640 root adm Into: create 644 root adm restart ...


0

crontab -e will edit that master file, don't edit /var/spool/cron/crontabs/tweaver manually, just do the above.


0

If you run in terminal: ./home/user/backup.sh you will get probably an error like: bash: ./home/user/backup.sh: No such file or directory That because in this case is not correct to use that . (dot) in front of the path to the scipt (/home/user/backup.sh). Also be sure that backup.sh is executable by running: chmod +x /home/user/backup.sh And also, ...


0

Problem solved. The cron job was running each night but not completing. The problem was with the script. The cron shell did not interpret "==" as equal, i.e. in the cron shell "1==1" was evaluated as false. However, when I ran the program at the command line it worked. I read somewhere that the bash shell understands == or = to mean equal... but the ...


0

This happens when you have multiple APT/DPKG instances running at the same time. If you run something that blocks apt-get like aptitude in GUI mode, and type sudo /etc/cron.daily/apt eventually it will fail with the same message.


0

My money's on Benoit for having the truly correct answer here, but as soon as you can verify that your script executes you will likely find some additional errors. In short, make sure you also check your environment! You're half way there by using variables that define the location of the commands (MYSQL="$(which mysql)") but which mysql just reads your ...


0

Ensure to run: sudo crontab -e (or crontab -e as root) And add the desired script: */15 * * * * /bin/bash /home/wayne/scripts/mysql_backup.sh This will initiate the cron every 15 minutes, obviously you may want to change that.


1

Unless you've skipped some characters when writting the syslog output in your question, it looks like you've made a typo in your CRON command by forgetting the / in front of the command that should looks like : /home/wayne/scripts/mysql_backup.sh


0

Just had a similar issue, and none of the above answers worked for me. I ended up simulating the problem with screen: * * * * * /usr/bin/screen -dm Add above line to cron, let it run once, turn it back off. Connect to your screen session (screen -r). If you are checking the screen session has been created (with ps) be aware that they are sometimes in ...


4

You can use DISPLAY=:0 notify-send `cat filename.txt` To display a message on screen. crontab itself doesn't know where to print that file. It has no terminal attached. Also it doesn't know to which DISPLAY to put info, so I put it manually.


0

I think files with extensions are ignored. run: run-parts --test /etc/cron.daily If you don't see your scripts listed, remove the .sh extensions and try again.


3

You don't have the necessary permissions to read other users' crontabs, either run as root or use sudo to invoke crontab -u, e.g. for user in $(cut -f1 -d: /etc/passwd); do sudo crontab -u $user -l; done or awk -F: '{print $1}' /etc/passwd | xargs -n1 sudo crontab -lu


1

If you have a fully qualified domain name for your server, this message should go away. In /etc/hosts, you can define a FQDN like ubun.somedomain.tld : 127.0.0.1 localhost 127.0.0.1 ubun.example.com ubun To apply the new host name without rebooting the system type (after having changed the /etc/hosts file) : $ sudo hostname ubun.example.com Then check ...



Top 50 recent answers are included