8 More Discussions You Might Find Interesting
1. Infrastructure Monitoring
Sorry if this is the wrong forum
Searching for Saas Monitor service which monitor my servers which are sitting in different providers .
This monitor tool will take as less CPU as possible , and will send info about the server to main Dashboard.
The info I need is CPU / RAM / my servers status (... (1 Reply)
Discussion started by: umen
1 Replies
2. Hardware
Hi, I am experiencing troubles with dual monitors in fedora 16. During boot time both monitors are working, but when system starts one monitor automatically shut down. It happend out of the blue. Some time before when I updated system this happend but then I booted older kernel release and... (0 Replies)
Discussion started by: wakatana
0 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I am trying to get some information from the sensors on my pc. But i get confuse with what i get.
I don t know where to find out which sensors watches what..
I use "sensors" under ubuntu 10.10.
Here is the result of the cmd line sudo sensors.
the temp 3 indicates 79°C which... (0 Replies)
Discussion started by: Mat_k
0 Replies
4. Shell Programming and Scripting
This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are... (1 Reply)
Discussion started by: genewolfe
1 Replies
5. UNIX for Dummies Questions & Answers
I just installed lm-sensor in my terminal and it's working, however i really don't know how to analyze what I have, Any help will be appreciated, Thanks
Here is the reading in my terminal,
sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0°C (crit = +124.0°C) ... (3 Replies)
Discussion started by: fvs
3 Replies
6. Shell Programming and Scripting
Hello,
I would like to write a script that use the display as an input.
In the display there is a list of file. I want to use it as an array and this would be the input in my script. Does somebody know how do I make it? (2 Replies)
Discussion started by: mig8
2 Replies
7. Shell Programming and Scripting
hi all
I am running a script monitor using source command.
the shell script monitor is used to execute a pl/sql procedure.
when i do
source monitor
and then
ps -ef | grep <procedure name>
i do not get any info
but when i do
sh monitor
and then
ps -ef | grep <procedure name>
i... (8 Replies)
Discussion started by: infyanurag
8 Replies
8. Solaris
In order to use a regular PC monitor would I need to do any configuration changes to my Ultra 5 box running Solaris 8 ? (1 Reply)
Discussion started by: mangolinux
1 Replies
SoDelayQueueSensor(3) Coin SoDelayQueueSensor(3)
NAME
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.
SYNOPSIS
#include <Inventor/sensors/SoDelayQueueSensor.h>
Inherits SoSensor.
Inherited by SoDataSensor, SoIdleSensor, and SoOneShotSensor.
Public Member Functions
SoDelayQueueSensor (void)
SoDelayQueueSensor (SoSensorCB *func, void *data)
virtual ~SoDelayQueueSensor (void)
void setPriority (uint32_t pri)
uint32_t getPriority (void) const
virtual void schedule (void)
virtual void unschedule (void)
virtual SbBool isScheduled (void) const
virtual SbBool isIdleOnly (void) const
virtual void trigger (void)
Static Public Member Functions
static uint32_t getDefaultPriority (void)
Protected Attributes
SbBool scheduled
Detailed Description
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.
The priority values can be used to queue events by their importance, so the sensors are triggered in the sequence you want.
The queue of delay sensors (i.e. instances of subclasses of SoDelayQueueSensor) will be processed as soon as either the run-time system is
idle, or if it is continually busy they will be processed within a fixed amount of time.
This time interval is by default 1/12th of a second, but can be controlled with the SoSensorManager::setDelaySensorTimeout() interface.
Constructor & Destructor Documentation
SoDelayQueueSensor::SoDelayQueueSensor (void)
Default constructor.
SoDelayQueueSensor::SoDelayQueueSensor (SoSensorCB *func, void *data)
Constructor taking as arguments the sensor callback function and the userdata which will be passed the callback.
See also:
setFunction(), setData()
SoDelayQueueSensor::~SoDelayQueueSensor (void) [virtual]
Destructor.
Member Function Documentation
void SoDelayQueueSensor::setPriority (uint32_tpri)
Set this sensor's priority in the scheduling queue. When sensors are processed, high priority sensors will trigger before low priority
sensors.
Please note that a low number means a high priority. A sensor with priority 5 will trigger before a sensor with priority 6.
Sensors with priority 0 have a special meaning in Coin/Inventor. They are called immediate sensors, and will trigger immediately after the
current notification chain has finished. Priority 0 sensors should be used with care, since they might lead to bad performance if you do
some processing in the sensor callback.
This setting does not affect SoDataSensor delete-callback invocations, which always are immediate.
See also:
getPriority(), getDefaultPriority()
uint32_t SoDelayQueueSensor::getPriority (void) const
Returns sensor scheduling priority.
See also:
setPriority(), getDefaultPriority()
uint32_t SoDelayQueueSensor::getDefaultPriority (void) [static]
Returns the default scheduling priority value. The default sensor priority is 100.
See also:
getPriority()
void SoDelayQueueSensor::schedule (void) [virtual]
Put the sensor in the global delay queue. This means it will be triggered either when the CPU is idle, or when the specified delay queue
time-out is reached.
See also:
SoDB::setDelaySensorTimeout(), unschedule(), isScheduled()
Implements SoSensor.
void SoDelayQueueSensor::unschedule (void) [virtual]
Remove sensor from the delay queue, without triggering it first.
See also:
schedule(), isScheduled()
Implements SoSensor.
SbBool SoDelayQueueSensor::isScheduled (void) const [virtual]
Check if this sensor is scheduled for triggering.
See also:
schedule(), unschedule()
Implements SoSensor.
SbBool SoDelayQueueSensor::isIdleOnly (void) const [virtual]
Returns a flag indicating whether or not the sensor should only be triggered if the application is truly idle, and not when the delay queue
is processed because of the delay queue timeout.
See also:
SoDB::setDelaySensorTimeout()
void SoDelayQueueSensor::trigger (void) [virtual]
Trigger the sensor's callback function.
Reimplemented from SoSensor.
Reimplemented in SoDataSensor, and SoFieldSensor.
Member Data Documentation
SbBool SoDelayQueueSensor::scheduled [protected]
TRUE if the sensor is currently scheduled.
Author
Generated automatically by Doxygen for Coin from the source code.
Version 3.1.3 Wed May 23 2012 SoDelayQueueSensor(3)