On a HP-UX 11.31 server I try to make a script that can launch glance for x iterations and the output to be stored in a file. I want to be able to launch the script via crontab.
glance manual says that in order to run glance in the background with no terminal screen displays I should use -adviser_only & -iterations options.
I tried this:
Issues:
- the job does not run in background, it displays everything on the terminal
- glance doesn;t stop automatically after 2 iterations.
indeed it sends the output to the /tmp/glance/glance.20160613 file and the file keeps the data after I stop glance.
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 FREEBSD
enigma
ENIGMA(1) BSD General Commands Manual ENIGMA(1)NAME
enigma, crypt -- very simple file encryption
SYNOPSIS
enigma [-s] [-k] [password]
crypt [-s] [-k] [password]
DESCRIPTION
The enigma utility, also known as crypt is a very simple encryption program, working on a ``secret-key'' basis. It operates as a filter,
i.e., it encrypts or decrypts a stream of data from standard input, and writes the result to standard output. Since its operation is fully
symmetrical, feeding the encrypted data stream again through the engine (using the same secret key) will decrypt it.
There are several ways to provide the secret key to the program. By default, the program prompts the user on the controlling terminal for
the key, using getpass(3). This is the only safe way of providing it.
Alternatively, the key can be provided as the sole command-line argument password when starting the program. Obviously, this way the key can
easily be spotted by other users running ps(1). As yet another alternative, enigma can be given the option -k, and it will take the key from
the environment variable CrYpTkEy. While this at a first glance seems to be more secure than the previous option, it actually is not since
environment variables can also be examined with ps(1). Thus this option is mainly provided for compatibility with other implementations of
enigma.
When specifying the option -s, enigma modifies the encryption engine in a way that is supposed to make it a little more secure, but incompat-
ible with other implementations.
Warning
The cryptographic value of enigma is rather small. This program is only provided here for compatibility with other operating systems that
also provide an implementation (usually called crypt(1) there). For real encryption, refer to bdes(1), openssl(1), pgp(1)
(ports/security/pgp), or gpg(1) (ports/security/gnupg). However, restrictions for exporting, importing or using such tools might exist in
some countries, so those stronger programs are not being shipped as part of the operating system by default.
ENVIRONMENT
CrYpTkEy used to obtain the secret key when option -k has been given
EXAMPLES
man enigma | enigma > encrypted
Enter key: (XXX -- key not echoed)
This will create an encrypted form of this man page, and store it in the file encrypted.
enigma XXX < encrypted
This displays the previously created file on the terminal.
SEE ALSO bdes(1), gpg(1), openssl(1), pgp(1), ps(1), getpass(3)HISTORY
Implementations of crypt are very common among UNIX operating systems. This implementation has been taken from the Cryptbreakers Workbench
which is in the public domain.
BSD May 14, 2004 BSD