LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 05-04-2010, 02:42 AM   #1
aarsh
Member
 
Registered: Mar 2010
Location: USA
Distribution: Ubuntu MATE
Posts: 182

Rep: Reputation: 18
schduling error


i wanna simply schedule a script's execution at specified time :
so I used :
admin@linux-fw4q:~> at 01:09PM May 4

but the output was following ..

warning: commands will be executed using /bin/sh
at> ./a.out
at> <EOT>
job 3 at 2010-05-04 13:09
Can't open /var/run/atd.pid to signal atd. No atd running? < --- why so ?
admin@linux-fw4q:~> ^CCan't open /var/run/atd.pid to signal atd. No atd running?
 
Old 05-04-2010, 03:04 AM   #2
aarsh
Member
 
Registered: Mar 2010
Location: USA
Distribution: Ubuntu MATE
Posts: 182

Original Poster
Rep: Reputation: 18
I want to schedule a script to run at a specifi time:
located at :

So, I used command as below and got error :

# at -f ScheduleDownload.sh -v 1:27
Wed May 5 01:27:00 2010

warning: commands will be executed using /bin/sh
job 6 at 2010-05-05 01:27
Can't open /var/run/atd.pid to signal atd. No atd running?

WHERE IS MY MISTAKE ??
 
Old 05-04-2010, 03:22 AM   #3
colucix
LQ Guru
 
Registered: Sep 2003
Location: Bologna
Distribution: CentOS 6.5 OpenSuSE 12.3
Posts: 10,509

Rep: Reputation: 1983Reputation: 1983Reputation: 1983Reputation: 1983Reputation: 1983Reputation: 1983Reputation: 1983Reputation: 1983Reputation: 1983Reputation: 1983Reputation: 1983
It means the at daemon is not running. Indeed OpenSuSE does not enable it by default. You can either a) run the at daemon for this specific task by issuing (as root)
Code:
/etc/init.d/atd start
then don't forget to stop it after completing your job:
Code:
/etc/init.d/atd stop
b) use crontab if applicable. The only advantage of at versus cron is that it retains your current login environment, whereas cron has a very limited one. There are methods to workaround these limitations anyway.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Memory error: extended error chipkill ecc error rajivdp Linux - Hardware 1 12-07-2009 08:26 AM
Sendmail: eocket wedge , 504 error , dsn error, mail relay connection error djcs Debian 0 03-03-2009 12:41 AM
PHP Error Parse error: parse error, unexpected $ in /home/content/S/k/i/SkinCare4U/h CowanServices Programming 2 12-09-2008 08:26 PM
Suse CUPS error: cups(File)DoRequest error:client-error-bad-request smdonelan Linux - Hardware 6 04-17-2007 06:46 PM
updating new installation of 9.3 ERROR...ERROR...ERROR Morbid SUSE / openSUSE 3 08-15-2005 11:22 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 12:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration