Sponsored Content
Full Discussion: Sun v215 Fan Speed
Operating Systems Solaris Sun v215 Fan Speed Post 302988500 by y33t on Tuesday 27th of December 2016 08:28:28 AM
Old 12-27-2016
What is the safest way to achieve this task ?
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

dmidecode, RAM speed = "Current Speed: Unknown"

Hello, I have a Supermicro server with a P4SCI mother board running Debian Sarge 3.1. This is the "dmidecode" output related to RAM info: RAM speed information is incomplete.. "Current Speed: Unknown", is there anyway/soft to get the speed of installed RAM modules? thanks!! Regards :)... (0 Replies)
Discussion started by: Santi
0 Replies

2. Solaris

Sun box's NIC speed setting

Is there a way to check if my Sun box's network interface card is set to 10 or 100 Mbps? Thanks! (1 Reply)
Discussion started by: FredSmith
1 Replies

3. BSD

Fan control

Hi all, Is there any way that I can get some control over th fan in my Evo N400C laptop running OpenBSD 4.0? Right now the fan is running constantly and it woulf be nice if it could be quiet sometime. (1 Reply)
Discussion started by: Timmy66
1 Replies

4. UNIX for Advanced & Expert Users

Unable to connect to Sunfire v215 box via XStart

SUN DataBase Server (Sunfire v215) Machine addresses Server IP:10.8.104.53 Server Mgmt IP:10.8.104.51 Server hostname:memstestdb OS passwords root:********* oracle:********* ALOM (Admin/Management) Machine IP: 10.8.104.51 ALOM account and password: admin:s@vi2005 (Note: at the... (2 Replies)
Discussion started by: jai111
2 Replies

5. Filesystems, Disks and Memory

data from blktrace: read speed V.S. write speed

I analysed disk performance with blktrace and get some data: read: 8,3 4 2141 2.882115217 3342 Q R 195732187 + 32 8,3 4 2142 2.882116411 3342 G R 195732187 + 32 8,3 4 2144 2.882117647 3342 I R 195732187 + 32 8,3 4 2145 ... (1 Reply)
Discussion started by: W.C.C
1 Replies

6. Solaris

Fan failure

would Solaris 10 shutdown automatically if both CPU fans fail? (7 Replies)
Discussion started by: orange47
7 Replies

7. Solaris

Sun Fire V240 server Fan replacement

I have a sun fire v240 server. The output of prtdiag -v shows a failed fan. There are 3 fans for cooling system board. There is 1 fan for each of the powersupply (There are 2 powersupplies) From the below output how do i know which fan is bad and whats its location... (3 Replies)
Discussion started by: Tirmazi
3 Replies

8. Hardware

How to remove fan from cpu fan chassis?

hi all, kindly help in this matter. Can i check anyone has any experience in removing the CPU fan from its chassis? my fan is spoilt and i wish to replace with other type. See picture below.. http://zone11.codemicroinc.netdna-cdn.com/large_1054367.jpg ---------- Post updated at 05:15 PM... (6 Replies)
Discussion started by: lchunleo
6 Replies

9. Solaris

Sun Fire V210 CPU Fan Temp too high?

Hey, I have a V210 with a failed CPU fan. The temperature is currently at 84C and I've been asked to wait a few weeks before replacing as its a production system and it cant be shut down yet. Is it too hot? Do I risk killing the CPU at this temp? Its been like this for a few weeks now... (5 Replies)
Discussion started by: magarvo
5 Replies

10. Solaris

Sun v215 ALOM Reset

Hi all, I got a v215 but the login credentials are unknown. I plug the serial management RS232-RJ45 and get the output on the terminal. I reseted NVRAM and battery but I can't use the default login still. After these operations the output from boot is as such ; ALOM POST 1.0 Status =... (21 Replies)
Discussion started by: y33t
21 Replies
iv_task(3)						    ivykis programmer's manual							iv_task(3)

NAME
iv_task_register, iv_task_unregister, iv_task_registered - deal with ivykis tasks SYNOPSIS
#include <iv.h> struct iv_task { void *cookie; void (*handler)(void *); }; void IV_TASK_INIT(struct iv_task *task); void iv_task_register(struct iv_task *task); void iv_task_unregister(struct iv_task *task); int iv_task_registered(struct iv_task *task); DESCRIPTION
The functions iv_task_register and iv_task_unregister register, respectively unregister, a task with the current thread's ivykis event loop. iv_task_registered on a task returns true if that task is currently registered with ivykis. A task is like a timer, but with an immediate timeout. When a task is registered, unless it is unregistered again first, the callback function specified by ->handler is guaranteed to be called once, in the thread that the task was registered in, some time after control returns to the ivykis main loop but before ivykis will sleep for more events, with ->cookie as its first and sole argument. When this hap- pens, the task is transparently unregistered. Tasks are mainly used for scheduling code for execution where it is not appropriate to directly run that code in the calling context (for example, because the current context might be run as a callback function where the caller expects certain conditions to remain invariant after the callback completes). The application is allowed to change the ->cookie and ->handler members at any time. A given struct iv_task can only be registered in one thread at a time, and a task can only be unregistered in the thread that it was regis- tered from. There is no limit on the number of tasks registered at once. See iv_examples(3) for programming examples. SEE ALSO
ivykis(3), iv_examples(3) ivykis 2010-08-15 iv_task(3)
All times are GMT -4. The time now is 06:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy