My perl script will not run under AT

mastersenpai · 06-26-2015, 04:38 PM

I am creating a bash script that will automatically open and close a perl script with the AT command. This is on RHEL 6 cli only. The problem I am having is that the perl script can't open automatically, but can open manually. I had a log created whenever there is an attempt that AT executes a process in the queue. This is what I got "TERM not set at /root/testscript.pl line 154"

TERM is set to undef, but I asked a colleague of mine and he says that the main issue is that the perl script needs to run on its own terminal. This is what the bash script looks like.

Code:

echo "setsid sh -c 'bash -c /root/testscript.pl <> /dev/tty4 >&0 2>&1'" | at 14:00
echo "pkill -INT testscript" | at 15:10
echo "setsid sh -c 'bash -c /root/testscript.pl <> /dev/tty4 >&0 2>&1'" | at 15:20
echo "pkill -INT testscript" | at 16:30
echo "setsid sh -c 'bash -c /root/testscript.pl <> /dev/tty4 >&0 2>&1'" | at 16:40
echo "pkill -INT testscript" | at 17:50

I also tried

Code:

echo "bash -c /root/testscript.pl > /dev/tty4" | at 14:00
echo "pkill -INT testscript" | at 15:10
echo "bash -c /root/testscript.pl > /dev/tty4" | at 15:20
echo "pkill -INT testscript" | at 16:30
echo "bash -c /root/testscript.pl > /dev/tty4" | at 16:40
echo "pkill -INT testscript" | at 17:50

I even replaced bash -c with /usr/bin/perl. Still no luck. Any suggestions?

fatmac · 06-27-2015, 03:48 AM

Just a thought, but might it be better using cron for this(?).

unSpawn · 06-27-2015, 04:16 AM

Quote:

Originally Posted by mastersenpai

The problem I am having is that the perl script can't open automatically, but can open manually.

Please explain what the PERL script actually does, if you have tried debugging it, if you have actually set the TERM variable (as it actually asks for it) and if you really need to test things as root user? (And I doubt running it via cron would change anything.)

mastersenpai · 06-27-2015, 11:30 AM

Quote:

Originally Posted by fatmac

Just a thought, but might it be better using cron for this(?).

I tried doing a cron job and it is the same result. Also, I don't want the script to run in a traditional pattern.

mastersenpai · 06-27-2015, 11:33 AM

Quote:

Originally Posted by unSpawn

Please explain what the PERL script actually does, if you have tried debugging it, if you have actually set the TERM variable (as it actually asks for it) and if you really need to test things as root user? (And I doubt running it via cron would change anything.)

It performs automated test calls to a FreeSWITCH server. I am doing everything in root. I tried googling what TERM variable I could change it to and even went to perldoc and couldn't find it.

NevemTeve · 06-27-2015, 01:47 PM

run complete scripts with at (not AT, by the way, that is something to do with modems):

Code:

$ cat dosomething.sh
#!/bin/sh

exec >>/tmp/debug.$$ 2>&1

set -xv

date

(actual commands)
$ echo './dosomething.sh' | at 14:00

On the other hand, if the problem exists in the 154th line of the perl-script, it cannot be solved via at

mastersenpai · 06-29-2015, 09:55 AM

Quote:

Originally Posted by NevemTeve

run complete scripts with at (not AT, by the way, that is something to do with modems):

Code:

$ cat dosomething.sh
#!/bin/sh

exec >>/tmp/debug.$$ 2>&1

set -xv

date

(actual commands)
$ echo './dosomething.sh' | at 14:00

On the other hand, if the problem exists in the 154th line of the perl-script, it cannot be solved via at

So then I take it that I can't be able to use the at command in the bash script and can only do that as an actual command? I'm still a little confused.

NevemTeve · 06-29-2015, 10:15 AM

I don't think I have suggested so... here is example I actually use:

Code:

#!/bin/sh

set -xv

TOMORROW=$(/usr/local/bin/gdate -d '+1 day' +'%Y%m%d')
WHEN="$TOMORROW"'0203'

at -t "$WHEN" <<DONE
/home/projects/hol/bin/e_somejob.stop.sh
/home/projects/hol/bin/e_somejob.start.sh
DONE