New answers tagged scheduling
Depends on the situation really. All things equal, I would prefer the GRUB approach, purely because it is simple and you get your chosen scheduler right at the start of the boot. The main issue with it is that it is a system wide setting and if you have more than one disk and want different schedulers on each, then it is no use. The udev approach is better ...
You are looking for a tool called rtcwake. It allows you to suspend your system and specify a specific wake up time. You can then set up a cronjob to play your song at a specified time. I found a nice example here: If I wanted my machine to sleep overnight, wake for a short maintenance, go to sleep again and wake early in the morning, I would have ...
From the MythTV's ACPI Wakeup wiki article. excerpt Your options Hardware timer switch - a cheap power switch and a simple cron job to shutdown the machine can do the job Wake on LAN - have another machine on your network wake your MythTV machine. (See the "Wake on LAN" MythTV HowTo) Use the real time clock (RTC) - most machines ...
You can send a magic packet to the computers MAC address. Notice that you need to enable this in your Bios. Then you can install wakeonlan via apt-get and use the following command to "wake" your system: wakeonlan 01:02:03:04:05:06 For your concern you need another machine to send this packet. For this there are several wake on lan services you can find ...
Fixed this issue. It was a permission issue of calling sh files from cron.
ammu you have to execute it using sh here is my example MAILTOfirstname.lastname@example.org 30 11 * * * sh /home/user/backup.sh 30 17 * * * sh /home/user/backup.sh have a look here cronjob
Actually nothing happens, because the int 3 is used only by debuggers to set breakpoints. In case you run your code with a debugger, then it also depends on the debugger what happens. As I used int 3 a couple of years ago, I missed support for lwp. I think if it is now supported, then it should only interrupt the affected thread.
The Google Groups post and @bersch's suggestion to look for the sched_setscheduler call directly (instead of the chrt command-line wrapper) got me to an answer: it was indeed because of my use of cpuset. I had forgotten that cgroups is used to support cpusets. A search for sched_getscheduler and cgroup turned up a ton of hits, including ...
Top 50 recent answers are included