Sponsored Content
Operating Systems Solaris Restored LDOM starts in June-2000 Post 302858111 by ad101 on Saturday 28th of September 2013 06:22:33 PM
Old 09-28-2013
Question Restored LDOM starts in June-2000

Hi Solaris Experts,

How to ensure restored LDOM start with correct date after power cycle?

When powered on, the primary came back with correct date (also correct in SP), then I restored the LDOMs
Code:
ldm create -i ldg1.xml
ldm bind ldg1
ldm start ldg1

but the date in ldg1 was June-2000 !
Code:
$ w;date -u
 11:23pm  up 1 min(s),  1 user,  load average: 1.43, 0.39, 0.14
User     tty           login@  idle   JCPU   PCPU  what
usr11    pts/1        11:23pm                      w
Tuesday, June  6, 2000 11:23:14 PM GMT

When restored, where does the LDOM set the date from?
How do I ensure the date is correct when restored?

If that's not feasible, how to ensure the LDOM starts in single-user mode?

This is on a T4-1 running Solaris 11.1, firmware, patch are current.

Thanks for your help.

ps: posted this on comp.unix.solaris too.

Last edited by ad101; 09-28-2013 at 07:50 PM..
 

4 More Discussions You Might Find Interesting

1. AIX

How to delete restored files?

I've just started with AIX interface (PASE) on iSeries system (AS/400). I've restored one bff file more than I need :). Is there any smart method to remove restored files. Maybe a smart script? (3 Replies)
Discussion started by: zukes
3 Replies

2. AIX

Can a pax backup in AIX be restored into Linux?

Dear all experts, I would like to know if a pax command backup of AIX files can be restored into Linux environment run in Wintel server? Currently I have a Full database backup using "pax" command in AIX box(IBM pSeries), the new management decison of the new server is on Wintel server which is... (5 Replies)
Discussion started by: kwliew999
5 Replies

3. Shell Programming and Scripting

Start copying large file while its still being restored from tape

Hello, I need to copy a 700GB tape-image file over a network. I want to start the copy process before the tape-image has finished being restored from the tape. The tape restore speed is about 78 Mbps and the file transfer speed over the network is about 45 Mbps I don't want to use a pipe, since... (7 Replies)
Discussion started by: swamik
7 Replies

4. Shell Programming and Scripting

Need to write a shell script that starts one, then kills it, then starts another?

This is on a CentOS box, I have two scripts that need to run in order. I want to write a shell script that calls the first script, lets it run and then terminates it after a certain number of hours (that I specify of course), and then calls the second script (they can't run simultaneously) which... (3 Replies)
Discussion started by: btramer
3 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 03:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy