Make sure your LPP_SOURCE is updated, then go through these steps:
Code:
smitty nim -->
Perform NIM Administration Tasks -->
Manage Resources -->
Perform Operations on Resources -->
Choose your spot -->
update_all -->
Source of Install Images --> Use "esc-3" to select your updated lpp_source
enter-->
enter
does somebody know about SPOT ?? any link about SPOT commands ?
i ve made a mistake during configuration, :mad:
then i ve started the system in Maintenance mode
the only shell was SPOT. :eek:
SPOT doesn t understand anything....
how do i work with SPOT ?
thanks in advance
Karine... :D (1 Reply)
I posted earlier with a problem it's here, I have edited the script a little and it tells me once more that the end of line is unexpected and I'm really lost with this one, thanks for any help.
The new version:
#!/bin/sh
case $# in
0) echo "Usage: enshar filename1 filename2 " >&2
;;... (20 Replies)
I try to migrate a NIM server from one server to another.
I try to do a mksysb on NIM server
restore the NIM server's mksysb to a client through NIM installation
shutdown NIM server
start newly installed client as NIM server
Does anyone do this before? who can give me some suggestion? (1 Reply)
Hello everyone
Im trying to backup a nim client from nim master but I got this message
COMMAND STATUS
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
0042-001 nim:... (2 Replies)
Hi.
I change my client's IP and hostname but I forgot to change anything on the master. How can I redefine or modify my client's resource from my master, or with using smit niminit from my client ?
Tks (2 Replies)
I have added our DR to NIM server and tried to create bosinstall image with smitty nim_bosinst command. But ended up with below error.
warning: 0042-229 m_bos_inst: When installing a system using a mksysb as the
source for the installation, the level of the SPOT used for the
... (3 Replies)
Hi there can anyone help me to spot my mistake and please explain why it appears
My code :
#!/usr/bin/gawk -f
BEGIN { bytes =0}
{ temp=$(grep "datafeed\.php" | cut -d" " -f8)
bytes += temp}
END { printf "Number of bytes: %d\n", bytes }
when I am running ./q411 an411
an411:
... (6 Replies)
Hi,
i backed up a test LPAR using mksyb utility on AIX. and transferred it to NIM server via NFS.
I want to create a SPOT using this mksysb . Please explain me the procedure. And got something online, but that procedure is different.
Please respond. (5 Replies)
Hello, I have an AIX6.1 machine which is a nim client to my nim master which is also AIX6.1 machine. I had some problem to perform an installation on my client using smit nim . i removed /etc/niminfo file in order to do the initialization again but when i run the command niminit -a name=client... (0 Replies)
Friend's,
I was playing around with NIM in my environment & had a quick question in mind which I didn't/couldn't find answer to, which is -- how to find the name of the NIM server sitting on the NIM client?
All leads to the answer would be much appreciated, many thanks!
-- Souvik (2 Replies)
Discussion started by: thisissouvik
2 Replies
LEARN ABOUT XFREE86
rsensor
RSENSOR(1) General Commands Manual RSENSOR(1)NAME
rsensor - compute sensor signal from a RADIANCE scene
SYNOPSIS
rsensor [ -n nprocs ][ -h ][ render options ] [ $EVAR ] [ @file ] { [ -rd nrays ][ -dn nsrc ][ sensor_view ] sensor_file .. } octree
rsensor [ -h ] { [ -rd nrays ][ sensor_view ] sensor_file .. } .
rsensor [ options ] -defaults
DESCRIPTION
Rsensor traces rays outward from one or more specified illumination sensors into the RADIANCE scene given by octree, sending the computed
sensor value to the standard output. (The octree may be given as the output of a command enclosed in quotes and preceded by a `!'.) In
the second form, a single period ('.') is given in place of an octree, and the origin and directions of the specified number of rays will
be printed on the standard output. If these rays are later traced and added together, the results will sum to a signal proportional to the
given sensor distribution. In the third form, the default values for the options (modified by those options present) are printed with a
brief explanation.
Options may be given on the command line and/or read from the environment and/or read from a file. A command argument beginning with a
dollar sign ('$') is immediately replaced by the contents of the given environment variable. A command argument beginning with an at sign
('@') is immediately replaced by the contents of the given file.
The sensor files themselves will be searched for in the path locations specified by the RAYPATH environment variable, similar to other
types of Radiance auxiliary files. If the sensor file path begins with '/', '.' or '~', no search will take place. Before each sensor
file, a separate view may be specified. In this case, the view origin and direction will correspond to the position and orientation of the
sensor, and the view up vector will determine the zero azimuthal direction of the sensor. The fore clipping distance may be used as well,
but other view options will be ignored. (See rpict(1) for details on how to specify a view.) The actual data contained in the sensor file
corresponds to the SPOT tab-separated matrix specification, where the column header has "degrees" in the leftmost column, followed by
evenly-spaced azimuthal angles. Each row begins with the polar angle, and is followed by the relative sensitivity values for each direc-
tion. A low-resolution example of a sensor file is given below:
degrees 0 90 180 270
0 .02 .04 .02 .04
45 .01 .02 .01 .02
90 .001 .002 .001 .002
As well as different views, the number of samples may be changed between sensors, where the -rd option controls the number of ray samples
sent at random, and the -dn option controls the number of rays sent to each light source per sensor.
The -h option toggles header output, which defaults to "on." The -n option may be used to specify multiple calculation processes on sys-
tems with more than one CPU. For additional options, consult the rtrace(1) man page. The final octree argument must be given, as the
octree cannot be read from the standard input.
EXAMPLES
To compute values for the same sensor with two different positions:
rsensor -ab 2 -vf posA.vf mysens.dat -vf posB.vf mysens.dat scene.oct
To generate a set of rays corresponding to a given sensor and compute the resulting signal with rtrace:
rsensor -h -vf posC.vf mysens.dat . | rtrace -h scene.oct | total -m
ENVIRONMENT
RAYPATH the directories to check for auxiliary files.
AUTHOR
Greg Ward for Architectural Energy Corporation
SEE ALSO oconv(1), rpict(1), rtcontrib(1), rtrace(1)RADIANCE 4/11/2008 RSENSOR(1)