As for your problems, are you sure you inputed -iterations -adviser_only,
I see no dash in your current command and looks like advisor_only should be adviser_only
Hope that helps
Best regards
Peasant.
thanks for the reply. I used this syntax also and got these results:
so the /tmp/glance/glance.20160613 is empty
Last edited by black_fender; 06-16-2016 at 05:29 AM..
Hi ,
I a stuck with this problem. I am trying to execute this script1 on SERVER 1 from SERVER 2 using script2
script1 on SERVER 1
#!/usr/bin/ksh
/opt/perf/bin/glance -f -adviser_only -iterations 2 -maxpages 2 > /home/user/scripts/glance.op
cpuval1=`grep ^CPU... (4 Replies)
Hello all,
I´m newbie using HP-GLANCEPlus. I readed the help screens provided but, I´m wonder if there are a user manual to use glance, or where can I find some usefull tips to use this tool better.
Anybody have some information?
Regards. (2 Replies)
Hi ALL - I need look to output data return from glance command but a don't have any access to HP-UX server. Maybe any HP-UX Admin send this data to my email (Removed.)
Thanks for help
Pawel (2 Replies)
I've been searching and cannot seem to find anywhere online a link to a manual for Glance.
Does anyone have a link to this? I searched in here already and the links I found on a post from 2002 were dead.
And more to the point, do you know if you can use Glance to see Disk I/O per logical... (2 Replies)
I am new to shell scripting.
Can someone explain me what this piece of code do..
/usr/bin/nohup /opt/perf/bin/glance -aos filename2.syntax -iterations 1 > filename.log (1 Reply)
Hello gurus,
I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired
report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup
is shown below:
#!/bin/ksh
db2... (3 Replies)
Discussion started by: okonita
3 Replies
LEARN ABOUT REDHAT
crond
CRON(8) System Manager's Manual CRON(8)NAME
cron - daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d/ directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
SEE ALSO crontab(1), crontab(5)AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 20 December 1993 CRON(8)