Glance file is empty.

[Eduard Pinales]

Hi.

I have is scripts run in crontab.

########################################
#!/usr/bin/ksh
fecha=`date | awk '{print $1$2$3$4}`
/opt/perf/bin/glance -f /adm/scripts/glancemonitor$fecha.txt -iterations 1

But the file that generate this scripts is empty. i need help.

Regards,

[Steven E. Protter · Accepted solution]

Shalom,

Probably:
No variables are being submitted.
date or awk command are failing because cron jobs have no PATH set.

Set a PATH in your script.

See whence to find PATH

SEP

[Eduard Pinales]

thanks,

But the problem is that file is empty when scripts is finished by cron. all variable are ok, because the file have the date when script finished.

[OFC_EDM]

I've learned to listen to Steven :)

When you cron a job you dont have an environment.

So when the script executes via cron it will not know where date and awk are located. Thus, the commands will fail.

Try setting a path or explicity call the commands as below

#!/usr/bin/ksh
fecha=`/sbin/date | /usr/bin/awk '{print $1$2$3$4}`
/opt/perf/bin/glance -f /adm/scripts/glancemonitor$fecha.txt -iterations 1

Note the path to the date and awk commands may differ on your system as these paths are from my Tru64 system.

if you don't know the path to the command type:
which date
which awk

It will display where it finds the command...as long as it's in the PATH of the user you're logged in as.

Otherwise use the find command to find where they are.

Cheers

[Eduard Pinales]

I did. but the problem not solve.

-rw-r--r--1 root sys 0 Oct 23 11:20 glancemonitorThuOct2311:20:00.txt

The script look as follow .
fecha=`/usr/bin/date | /usr/bin/awk '{print $1$2$3$4}`
/opt/perf/bin/glance -f /adm/scripts/glancemonitor$fecha.txt -iterations 1

Regards

[Torsten.]

I think the problem is somewhere else.

Re-direct the error channel to a file!

I assume something like this:

# export TERM=xx
# glance -f /tmp/t1 -iterations 1

Welcome to Glance


Sorry, I don't know anything about your "xx" terminal.





IMHO your result will be similar!

[Torsten.]

See

man glance

on how to run it in background.

[Torsten.]

Well, it's the output channel, not the error channel.

# glance -f /tmp/t1 -iterations 1 >/tmp/t2
# more /tmp/t2
Sorry, I don't know anything about your "xx" terminal.

Welcome to Glance


You will probably find related massages in

# more /var/adm/cronlog

[Eduard Pinales]

the problem is same. The file is empty when the cron run the script.

[Torsten.]

I'm not sure if you understand - a cronjob has no terminal


-> glance will not run!

See

man glance

on how to run glance without a terminal (in background).

[Eduard Pinales]

Glance not run in Background, but exist any flag to help it run in background for example -adviser_only , etc. i put it, but the problem is the same.

Regards,

[Torsten.]

Does

# man glance

not work on your system???

I copy a part of this for you:

" To run GlancePlus in the background against special adviser syntax,
logging data to a file, you must first create a file that contains the
appropriate adviser commands, then execute GlancePlus with stdout
redirected to a file. For example:
echo 'print gbl_stattime, " runq=", gbl_run_queue' >temp
glance -aos ./temp -j 60>outfile &
"

[Eduard Pinales]

Ok thanks,

But i need the specific PID. how do i do that ?. not total all. i need to view the utility for every PID.

[OFC_EDM]

I'm curious about whether you get any output from

/opt/perf/bin/glance -iterations 1

Not sure if that's a valid command as I don't have glance available. Basically I want to know if you get output if you don't specify an output file.

My thought is there's no sense trying to redirect to a file if the base command doesn't provide output. Could you confirm that you do get output with the basic command?

Cheers