10-07-2008
That sounds like a good idea, but since I am looking to automate this, how could I determine when the appropriate time to remove it from dhcp is? I am developing an application that drives this so I wouldn't be able to put a specific time limit (as we know it can vary from system to system), what I need is some trigger or event that indicates the client has successfully finished the boot process. Any thoughts?
10 More Discussions You Might Find Interesting
1. Solaris
Hi
I just configured a jumpstart server for x86 and sparc clients. I don't use a dhcp server, so I configured /etc/ethers and did add_install_client to update /etc/bootparams. The sparc installation ist working, but the x86 installation stops after CD1 was successfully installed.
What I did:
I... (2 Replies)
Discussion started by: Jay_Fisi
2 Replies
2. Solaris
I need a little help figuring out why my custom jumpstart network installation is dumping me to a manual install.
I am trying to install Solaris 10 (unattended) over the wire from my jumpstart server to an HP Proliant DL380 server but I'm having difficulties with the unattended part.
So, what... (2 Replies)
Discussion started by: alias.256
2 Replies
3. Solaris
Does anyone know how to Jumpstart a Solaris 10 x86 system without the GUI?
I would like to keep the Jumpstart and/or Flash Archive install in a console text mode if possible but I've not had much luck finding instructions. I'm guessing this is going to be accomplished from the grub menu with a... (5 Replies)
Discussion started by: alias.256
5 Replies
4. Solaris
Can I use a Jumpstart enviroment on x86 to install a sparc64 client?
The idea is to install Solaris in an virtual environment (Sun Virtual Box) running on a pc (AMD), configure a Jumpstart server, and have a SUN Ultra 60 (sparc64) installed via the Jumpstart server.
The SUN has no cdrom... (4 Replies)
Discussion started by: eldiablo
4 Replies
5. Solaris
Hi All,
Is there a possible way to fully automate Solaris x86 jumpstart or make the x86 jumpstart unattended?
I'm currently checking the possible options on how can I do the x86 jumpstart to be kicked off during midnight.
We have an automated jumpstart (start to run from midnight) for... (2 Replies)
Discussion started by: racbern
2 Replies
6. Solaris
Hi friends ,
i have on ultra 10 Sparc machine . Due to some problem my OS is fully corrupted , so i am planning to install again but my problem is the cd drive in Ultra 10 machine is not working.
Now i am planning to use Jumpstart installation method to install my server.
But i... (4 Replies)
Discussion started by: vr_mari
4 Replies
7. Solaris
client boots fine, it gets the ip 192.168.0.10 and the bootfile. Then there is :
SunOS 5.10 Version Generic_141445-09 32-bit"
...
Configuring devices.
Custom JumpStart
Reading ZFS config: done
Setting up Java. Please wait ...
NOTE: Not enough memory for graphical installation. Graphical... (4 Replies)
Discussion started by: TomSu
4 Replies
8. Solaris
I have a jumpstart client that is not requesting the tftp boot file. The rarp function is working, hostname and ip are set ok, but it hangs after that.
tcpdump output:
jumpstart-server:/var/lib/tftpboot# tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol... (6 Replies)
Discussion started by: skitch
6 Replies
9. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
10. Solaris
Installing Solaris x86 using jumpstart does not set the hostname for the target. Any idea where do we need to specify hostname to be set for jumpstart installation. (1 Reply)
Discussion started by: hemalsid
1 Replies
LEARN ABOUT DEBIAN
sensors
Sensor Classes(3) Coin Sensor Classes(3)
NAME
Sensor Classes -
Classes
class SoAlarmSensor
The SoAlarmSensor class is a sensor which will trigger once at a specified time.
SoAlarmSensor provides a convenient way of setting up triggers for jobs which should be executed only once when they are scheduled. "
class SoDataSensor
The SoDataSensor class is the abstract base class for sensors monitoring changes in a scene graph.
If you need to know when a particular entity (as a field or a node) changes, subclasses of SoDataSensor can be used to monitor the entity
and notify you when it changes. "
class SoDelayQueueSensor
The SoDelayQueueSensor class is the abstract base class for priority scheduled sensors.
Delay queue sensors are invoked upon various events not related to time occurrences. See documentation of subclasses to see which types of
events can be surveilled by the builtin sensor types. "
class SoFieldSensor
The SoFieldSensor class detects changes to a field.
Attach a field to a sensor of this type to put it under surveillance, so you can act upon changes to the field. "
class SoIdleSensor
The SoIdleSensor class is a sensor which will trigger as soon as the application is idle.
An SoIdleSensor differs from an SoOneShotSensor in that it will not trigger if the delay queue processing is occurring due to the delay
queue timeout, but only when the application is idle. "
class SoNodeSensor
The SoNodeSensor class detects changes to nodes.
Attach a node to a sensor of this type to put it under surveillance, so you can act upon changes to the node. "
class SoOneShotSensor
The SoOneShotSensor class is a sensor which will trigger once.
Since SoOneShotSensor is a subclass of SoDelayQueueSensor, it will trigger as soon as either the run-time system is idle, or if it is
continually busy it will trigger within a fixed amount of time (this is by default 1/12th of a second, see
SoSensorManager::setDelaySensorTimeout()). "
class SoPathSensor
The SoPathSensor class detects changes to paths.
If you need to know when a path changes (i.e. nodes in the path has been removed, or new nodes is added), use this sensor to get a
notification. "
class SoSensor
The SoSensor class is the abstract base class for all sensors.
Sensors is a mechanism in Coin for scheduling jobs to be run upon specific events. The events in question could be particular points in
time, or changes to entities in the scene graph. "
class SoSensorManager
The SoSensorManager class handles the sensor queues.
There are two major sensor types in Coin, 'delay' sensors and 'timer' sensors: "
class SoTimerQueueSensor
The SoTimerQueueSensor class is the abstract base class for sensors triggering on certain timer events.
Timer sensors triggers upon specific points in time. "
class SoTimerSensor
The SoTimerSensor class is a sensor which will trigger at given intervals.
Use sensors of this class when you want a job repeated at a certain interval, without explicitly needing to reschedule the sensor (i.e.
SoTimerSensor automatically re-schedules itself after it has been triggered). "
Detailed Description
Sensors are objects that monitor other objects for changes and invoke callbacks when changes occur.
Author
Generated automatically by Doxygen for Coin from the source code.
Version 3.1.3 Wed May 23 2012 Sensor Classes(3)