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
GEARMAN_TASK_DATA_SIZE(3)					     Gearmand						 GEARMAN_TASK_DATA_SIZE(3)

NAME
gearman_task_data_size - Gearmand Documentation, http://gearman.info/ SYNOPSIS
#include <libgearman/gearman.h> gearman_task_st void gearman_task_free(gearman_task_st *task) void *gearman_task_context(const gearman_task_st *task) void gearman_task_set_context(gearman_task_st *task, void *context) const char *gearman_task_function_name(const gearman_task_st *task) const char *gearman_task_unique(const gearman_task_st *task) const char *gearman_task_job_handle(const gearman_task_st *task) bool gearman_task_is_known(const gearman_task_st *task) bool gearman_task_is_running(const gearman_task_st *task) uint32_t gearman_task_numerator(const gearman_task_st *task) uint32_t gearman_task_denominator(const gearman_task_st *task) void gearman_task_give_workload(gearman_task_st *task, const void *workload, size_t workload_size) size_t gearman_task_send_workload(gearman_task_st *task, const void *workload, size_t workload_size, gearman_return_t *ret_ptr) const void *gearman_task_data(const gearman_task_st *task) size_t gearman_task_data_size(const gearman_task_st *task) void *gearman_task_take_data(gearman_task_st *task, size_t *data_size) size_t gearman_task_recv_data(gearman_task_st *task, void *data, size_t data_size, gearman_return_t *ret_ptr) const char *gearman_task_error(const gearman_task_st *task) New in version 0.21. gearman_return_t gearman_task_return(const gearman_task_st *task) New in version 0.21. Link with -lgearman DESCRIPTION
A gearman_task_st represents a task. Work that is sent by a client to a gearman server is seen as a task (a worker recieves a task in the form of a job. Tasks, i.e. gearman_task_st are created by calling either gearman_execute(), gearman_client_add_task(), or gearman_client_add_task_back- ground(). gearman_client_add_task_status() can also create gearman_task_st, these tasks will be used to monitor a previously created gearman_task_st. gearman_task_free() is used to free a task. This only needs to be done if a task was created with a preallocated structure or if you want to clean up the memory of a specific task. gearman_task_set_context() sets the given context of the gearman_task_st. The context can be used to pass information to a gearman_task_st. gearman_task_context() returns the context that was used in the creation of the gearman_task_st (or that was set with gearman_task_set_context(). gearman_task_data() returns the current data that has been returned to the task. gearman_task_data_size() will give you the size of the value. gearman_task_take_data() is the same as gearman_task_data() but the value that is returned must be freed by the client (free(3)). gearman_task_recv_data() can be used with pre-allocated buffers. gearman_task_is_known(), gearman_task_is_running(), gearman_task_numerator(), and gearman_task_denominator(), return values related to the last status update that was made to the gearman_task_st. They do not cause the gearman_task_st to update itself. gearman_task_error() return the last error message that the gearman_task_st encountered. gearman_task_return() return the last gear- man_return_t stored. A value of GEARMAN_UNKNOWN_STATE means that the task has not been submitted to server yet, or that no function was available if the job has been submitted. RETURN VALUE
Various. Values that are returned by gearman_task_take_data() must have free(3) called on them. HOME
To find out more information please check: http://gearman.info/ SEE ALSO
gearmand(8) libgearman(3) AUTHOR
Data Differential http://www.datadifferential.com/ COPYRIGHT
2012, Data Differential, http://www.datadifferential.com/ 0.33 May 04, 2012 GEARMAN_TASK_DATA_SIZE(3)
All times are GMT -4. The time now is 09:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy