Setting up an atjob.
arimo at iki.fi
Sun Jan 20 20:22:37 UTC 2013
Have a look to crontab command too. It might be easier to set up if you
have fixed events on every day or on certain days of week.
mr. M01510 & guide Loadstone-GPS
Lat: 62.38718, lon: 25.64672
0C1F 6A76 DC9D DD58 3383 8B5D 0E76 9600 B784 D02
Anders Holmberg kirjoitti> Hi!
> Thanks for all help on this.
> Will try this to night.
> I will use it as a simple alarm for me to wake up.
> I haven't found any good alarmclocks out there for command lines.
> 20 jan 2013 kl. 14:51 skrev Tim Chase <blinux.list at thechases.com>:
>> On 01/20/13 07:35, Hart Larry wrote:
>>> And lastly, you would hit a control+d to finish a job.
>>> I hope I got all of this accurately for you-and-all of us
>> You're accurate :-)
>> Though it can be done several ways. Hart's method is more interactive, as you can type multiple commands for the system to issue at that time.
>> You can also pipe the commands to "at", either directly using "echo" like Anders & I do, or by putting those commands in a file and piping those commands to at:
>> at 8am < commands.txt
>> There are a couple other gotchas, some of which are obvious, some of which are less so:
>> 1) running X programs sometimes require a little bit of extra trickery. You might have better luck running "play" or "aplay" instead of mplayer
>> 2) obviously, this runs on the machine where you enqueue the job. So if you're remoted into your home machine from work, and you enqueue the job there, it will run at home (and thus play sound there, rather than work). I'm sure this is obvious, but I just figured I'd make sure that it was spelled out.
>> Blinux-list mailing list
>> Blinux-list at redhat.com
> Blinux-list mailing list
> Blinux-list at redhat.com
More information about the Blinux-list