AT not working

Fixit7 · 12-16-2014, 01:35 AM

I can not get "at" to work.

Geany never opened. ??

Code:

# at 1:31 am
warning: commands will be executed using /bin/sh
at> geany
at> <EOT>
job 4 at Tue Dec 16 01:31:00 2014

wpeckham · 12-16-2014, 06:05 AM

User Error. You are attempting to open a user interface in an environment with no tty or xWindows access.
You may have misunderstood what at is for.
Think a detached, background batch shell environment that is NOT interactive and has not terminal connected.

Fixit7 · 12-16-2014, 11:55 AM

I don't understand what you are saying.

According to this site, at should be working.

http://www.brunolinux.com/02-The_Ter...t_Command.html

rigor · 12-16-2014, 12:45 PM

Hi Fixit7,

Generally speaking, at runs programs in the background that do not require Human interaction.

By default there is no display. So if you are trying to run something that requires a display, you might well have problems.

Fixit7 · 12-16-2014, 01:00 PM

O.K., but this example does not work.

Maybe the author is mistaken or they have changed at ?

Quote:

$ at 12:49 -m
warning: commands will be executed using (in order) a) $SHELL b) login shell c) /bin/sh
at> play /usr/share/sounds/KDE_Startup.wav
at> <EOT>
job 7 at 2006-05-01 12:49

rigor · 12-16-2014, 05:03 PM

This is the output I get when I try to run the play command directly.

Code:

play FAIL formats: can't open input file `/usr/share/sounds/KDE_Startup.wav': No such file or directory

So when you say the command does not work, exactly what happens when the at job runs?

rigor · 12-16-2014, 05:10 PM

Maybe this will illustrate the situation:

Code:

$ tty
/dev/pts/5
$ date
Tue Dec 16 17:06:29 CST 2014
$ at 17:07
warning: commands will be executed using /bin/sh
at> echo 'Hello from an at job'  >> /dev/pts/5
at> <EOT>
job 6 at Wed Dec 17 17:07:00 2014
$ Hello from an at job

Fixit7 · 12-16-2014, 05:49 PM

Quote:

Originally Posted by rigor

This is the output I get when I try to run the play command directly.

Code:

play FAIL formats: can't open input file `/usr/share/sounds/KDE_Startup.wav': No such file or directory

So when you say the command does not work, exactly what happens when the at job runs?

You probably do not have that wav file.

Try one you know you have.

Fixit7 · 12-16-2014, 05:52 PM

# at 17:53
warning: commands will be executed using /bin/sh
at> echo 'Hello' >> /dev/pts/0
at> <EOT>
at> <EOT>
job 9 at Tue Dec 16 17:53:00 2014
Can't open /var/run/atd.pid to signal atd. No atd running?

SAbhi · 12-16-2014, 09:23 PM

well it depends which OS you use and what works on that to play audio files:

Code:

# at 08:47 am today
at> aplay /usr/share/sounds/alsa/Rear_Right.wav >/dev/pts/1
at> <EOT>
job 11 at 2014-12-17 08:47

worked perfectly fine for me. see the highlighted

Below many known commands wont work, so OS to OS matters what's available:

Code:

# aplay /usr/share/sounds/alsa/Rear_Right.wav
Playing WAVE '/usr/share/sounds/alsa/Rear_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono

# play /usr/share/sounds/alsa/Rear_Right.wav
-bash: play: command not found

# audioplay /usr/share/sounds/alsa/Rear_Right.wav
-bash: audioplay: command not found

rigor · 12-16-2014, 11:21 PM

Quote:

Originally Posted by Fixit7

You probably do not have that wav file.

Try one you know you have.

Of course I don't have the file. But since you were just indicating that at didn't work, but not saying what the failure was, it was hard for other people to understand what issue you were having.

rigor · 12-16-2014, 11:23 PM

Quote:

Originally Posted by Fixit7

# at 17:53
warning: commands will be executed using /bin/sh
at> echo 'Hello' >> /dev/pts/0
at> <EOT>
at> <EOT>
job 9 at Tue Dec 16 17:53:00 2014
Can't open /var/run/atd.pid to signal atd. No atd running?

That can happen when the at daemon atd is not running.
Do you have atd running?

Fixit7 · 12-16-2014, 11:36 PM

From what I understand, atd should run each time my system is started.

I have at-3.1 installed.

rigor · 12-16-2014, 11:42 PM

Fixit7,

If you look at the first aplay SAbhi you'll see that it was connected to a terminal by using the sequence:

Code:

>/dev/pts/1

which is what I did with the echo command I showed in a previous post.

at generally runs things in the background without a controlling terminal. So if something you want at to run needs a terminal for output, you'll generally want to connect it to one.

Also, naturally you need the at Daemon atd running.

HTH!

Fixit7 · 12-16-2014, 11:50 PM

Thanks rigor.

So, how do I get atd to run ?