'at' behaves strange

[Pita]

In my rescued VL6 box 'at' is now acting strangely.  When started it shows in the
CPU monitor a running taking a large junk of the % CPU used. It will only stop with
command 'at stop'.

I removed 'at' and reinstalled it  and nothing changed.

Any ideas how to correct?

[Pita]

I went around it by having cron execute 'atrun' every 15 min. 

[Joe1962]

I have never actually used "at", but I remembered there was a fix a broken "at" posted back in VL6 SOHO Beta 4 days, I don't know if this is at all relevant for your issue with VL6 Std though.

The fix was to do the following as root:

Code:

touch /var/spool/atjobs/.SEQ
chmod 660 /var/spool/atjobs/.SEQ
chown daemon.daemon /var/spool/atjobs/.SEQ
chmod 640 /etc/at.deny
chown root.daemon /etc/at.deny

[Pita]

I have never actually used "at", but I remembered there was a fix a broken "at" posted back in VL6 SOHO Beta 4 days, I don't know if this is at all relevant for your issue with VL6 Std though.

The fix was to do the following as root:

Code:

touch /var/spool/atjobs/.SEQ
chmod 660 /var/spool/atjobs/.SEQ
chown daemon.daemon /var/spool/atjobs/.SEQ
chmod 640 /etc/at.deny
chown root.daemon /etc/at.deny

Nope above changed nothing. The moment I start 'at' it eats up CPU usage.

I like 'at'. It is fast. Coming from the dentist in a terminal type:

at now +6 month
enter commands like a sound, followed by xmessage for a message
then finish with
Ctrl+d

and exactly in 6 months it will remind you to go to the dentist, if that was your message.

If have tried various schedulers and never was able to figure them out
being gui challenged.