[Wien] Warning: at daemon not running

[reza sotudeh]

 Dear Gerhard
>> We checked the at.allow and at.deny. The problem is not due to these files
>> too.
>>  your
>>
>> Reza Sotudeh
>> *reza sotudeh <sotudeh.reza at gmail.com>* wrote:
>>
>> Hi
>> Dear Dr. Jalali
>> This is the first response to our qestion.I hope this help us.
>> Thank you.
>> regards.
>>
>> Reza Sotudeh
>>
>> check the files
>>> at.allow and at.deny, maybe you are not allowed to use it.
>>> On some systems the user that likes to use at or batch needs in addition
>>> to be in the group at.
>>> The demon should be started during the boot sequence and not every time
>>> you like to use it.
>>>
>>> Ciao
>>> Gerhard
>>> ________________________________________
>>> Von: wien-bounces at zeus.theochem.tuwien.ac.at [
>>> wien-bounces at zeus.theochem.tuwien.ac.at] im Auftrag von reza sotudeh [
>>> sotudeh.reza at gmail.com]
>>> Gesendet: Dienstag, 10. Juni 2008 10:48
>>> An: Wien at zeus.theochem.tuwien.ac.at
>>> Betreff: [Wien] Warning: at daemon not running
>>>
>>> Dear All,
>>> We would run our program using at daemon. We see the following error
>>> after pushing CTRL+D:
>>>
>>> Warning: at daemon not running
>>>
>>> We then tried to restart the atd service as follows:
>>> [root at localhost ~]# /etc/init.d/atd restart
>>> Stopping atd:                                              [FAILED]
>>> Starting atd:                                              [  OK  ]
>>>
>>> as you see the service is up. But again we got the last error, i.e.,
>>> Warning: at daemon not running.
>>> Then we tried to stop the service of atd. The result is:
>>> [root at localhost ~]# /etc/init.d/atd stop
>>> Stopping atd:                                              [FAILED]
>>>
>>> So we wonder why we cannot stop the bringing up service atd.
>>> We then tried to make a trick. Our trick is:
>>>  echo 1234 >/var/run/atd.pid
>>> then we tried to bringing up the service again:
>>> [root at localhost ~]# /etc/init.d/atd restart
>>> Stopping atd:                                              [FAILED]
>>> Starting atd:                                              [  OK  ]
>>>
>>> after this we observe that the at daemon does work.
>>> We thought that the problem is fixed. But unfortunately we observed the
>>> problem again by resubmitting another job.
>>> So we tried once more the above procedure. Sometime the above discussed
>>> procedure works well, and sometime it fails.
>>> We tried to reinstall the atd service, as we just thought that maybe the
>>> problem comes from the atd service. But this also could not help.
>>> We changed on another machine,  which at daemon there worked well, the
>>> stack size to unlimited. Then we found that the at daemon also on this
>>> machine fails to work.
>>>
>>> We appreciate if you help us to fix this sever unexpected problem.
>>> Your,
>>> M. Sotudeh
>>>
>>> _______________________________________________
>>> Wien mailing list
>>> Wien at zeus.theochem.tuwien.ac.at
>>> http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
>>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://zeus.theochem.tuwien.ac.at/pipermail/wien/attachments/20080610/71cfd24d/attachment-0001.html