Sponsored Content
Operating Systems Solaris Automatic reboot does not work after power failure Post 302256581 by incredible on Monday 10th of November 2008 06:50:29 AM
Old 11-10-2008
dont pray for a power failure. Its best not to have one Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Reboot the Unix work station

Hi I'd like to know if to reboot a work station I need the root permission. If not what is the procedure ( commands or steps ) to reboot a work station. Cheers Mohsen (5 Replies)
Discussion started by: mohsen
5 Replies

2. UNIX for Dummies Questions & Answers

Restart on power failure

How do I configure my workstation (Solaris 9) to restart and perform any check disk automatically if there is a power failure? Thanks. (1 Reply)
Discussion started by: here2learn
1 Replies

3. UNIX for Advanced & Expert Users

sys-unconfig doesn't work after reboot

Hi All! I'm running "Solaris 10 10/08 s10s_u6wos_07b SPARC" on M5000. I ran sys-unconfig and after the machine rebooted the system did not prompt me for configuration info (system name, ip address, etc). I have also modified /etc/.sysIDtool.state changing all "1" to "0" and touch... (1 Reply)
Discussion started by: bluescreen
1 Replies

4. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

5. Solaris

Automatic startup of SSH at reboot ?

hi friends, any idea how do we configure a automatic startup of SSH services in Solaris boot ? (5 Replies)
Discussion started by: Exposure
5 Replies

6. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

7. Solaris

After power failure, SunFireV240 with SOLARIS 5.9 cannot start

SUNW, Sun Fire V240 Spare Sun OS Release 5.9 After a power failure we try to start the server We have the following messages: Thanks for your assistance (7 Replies)
Discussion started by: doudou2012
7 Replies

8. Emergency UNIX and Linux Support

Reboot does not work after update

Hi guys, thanks for your help. I recently did a yum update on my rhel6.4 server. After this update, user logins take for ever and the reboot command does not work. When I do a reboot, the server hangs. Nothing happens. Any help with this will be appreciated. Thank you (3 Replies)
Discussion started by: cjashu
3 Replies

9. UNIX for Dummies Questions & Answers

Power failure: file damage?

~#hello -all, Many UNIX/Linux/BSD/etc books warn about turn off the puter without a proper shutdown. This can damage files which are open at that moment. Seems logical to me. My question is.. does the system warn you when there are damaged files when the system is up again? I had a power failure... (7 Replies)
Discussion started by: raylier
7 Replies

10. AIX

Automatic Server bootup after power outage?

Hi everyone, We had a power outage few days ago, and I got the servers up and running but I was informed to look into, if there is a way to bring up the servers automatically/defaultly. I was told the windows admin has their server set up where the servers are up automatically if there is a... (11 Replies)
Discussion started by: Adnans2k
11 Replies
power(9E)							Driver Entry Points							 power(9E)

NAME
power - power a device attached to the system SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> int prefixpower(dev_info_t *dip, int component, int level); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If the driver writer does not supply this entry point, the value NULL must be used in the cb_ops(9S) structure instead. PARAMETERS
dip Pointer to the device's dev_info structure. component Component of the driver to be managed. level Desired component power level. DESCRIPTION
The power(9E) function is the device-specific Power Management entry point. This function is called when the system wants the driver to set the power level of component to level. The level argument is the driver-defined power level to which the component needs to be set. Except for power level 0, which is inter- preted by the framework to mean "powered off," the interpretation of level is entirely up to the driver. The component argument is the component of the device to be power-managed. The interpretation of component is entirely up to the driver. When a requested power transition would cause the device to lose state, the driver must save the state of the device in memory. When a requested power transition requires state to be restored, the driver must restore that state. If a requested power transition for one component requires another component to change power state before it can be completed, the driver must call pm_raise_power(9F) to get the other component changed, and the power(9E) entry point must support being re-entered. If the system requests an inappropriate power transition for the device (for example, a request to power down a device which has just become busy), then the power level should not be changed and power should return DDI_FAILURE. RETURN VALUES
The power() function returns: DDI_SUCCESS Successfully set the power to the requested level. DDI_FAILURE Failed to set the power to the requested level. CONTEXT
The power() function is called from user or kernel context only. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), cb_ops(9S) Writing Device Drivers Using Power Management SunOS 5.10 12 Dec 2003 power(9E)
All times are GMT -4. The time now is 11:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy