Sponsored Content
Full Discussion: Using flar
Operating Systems Solaris Using flar Post 303017062 by hicksd8 on Tuesday 8th of May 2018 03:17:27 PM
Old 05-08-2018
To answer your question flash archives do not need to be created in single user mode. They can be created in multi-user mode BUT you should do that when the system is as quiet as possible, not under load.
This User Gave Thanks to hicksd8 For This Post:
 

9 More Discussions You Might Find Interesting

1. Solaris

Flar Images

I once found a document on the web describing how to build partition flar images instead of having just the one large one. I have managed this but am having problems extracting the subsequent flar archives. I ahve built the system from a jumpstart server and now need to add the program images etc... (0 Replies)
Discussion started by: 58fairlane
0 Replies

2. Solaris

unable to create flar

Hello friend, Now i'm doing JDS3.1 in v440 servers.while checking the lustatus command getiing out like this lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- --------... (0 Replies)
Discussion started by: rjay.com
0 Replies

3. Solaris

Jumpstart / Flar problems Solaris 10 8/07

Hi, Im trying to make a jumpstart dvd using an flar archive. I have done this before on earlier releases of Solaris 10 (Sparc). Im now trying to do the same with the 8/07 release.. Problem : After the server is installed (during first boot ) the Select keyboard layout dialog appears. I... (5 Replies)
Discussion started by: s93366
5 Replies

4. Solaris

Jumpstart with flars: looking for /tmp/flar

I'm a little stumped here. If anyone has seen this, please point me in the right direction Little background first: I maintain a Solaris corporate build, currently based on Solaris 10u4 (08/07). This build is deployed using flars through jumpstart, wanboot, and jumpstart DVD. In the lab, I have... (1 Reply)
Discussion started by: System Shock
1 Replies

5. Solaris

FLAR Tape Backup/Restore

I have a T2000 server that is JumpStarted with Solaris 10 from the JumpStart server. Host name and IP address is changed after that. Then we backup the server using FLAR to tape: root.damas# date; flarcreate -c -t -n "Sol10_cairo_image" -a "engineering@starsolutions.com" -R / /dev/rmt/0n ;... (2 Replies)
Discussion started by: StarSol
2 Replies

6. Solaris

flar on linux???

Hi admins, As we can create flash archieve on solaris with flarcreate command utility, so is there any utility like this on Linux to create flah archieves ?? (10 Replies)
Discussion started by: snchaudhari2
10 Replies

7. Solaris

"flar create" produces a tiny flar image of rpool

Hi, can someone help with the following? I got 1x146GB disk which is span by just one zfs rpool. When issue for example: as you can see in above output the flar is very small, just around 10KB rpool with all data sets has several GB so this can't be good image. This is on the Solaris 10... (3 Replies)
Discussion started by: TomSu
3 Replies

8. Solaris

Solaris 8 Flar Creation/Restore

I'm new to utilizing Solaris... especially the old 8 version, but I'm trying to find out if there is a way to create a Flash Archive of a disk that can be restored on a smaller size disk or disk of varying size? (2 Replies)
Discussion started by: scifi_vixen
2 Replies

9. Solaris

Solaris 10 Restore from flar image

Hi! I want to migrate Sun Fire v240 server (sun4u) with Solaris 10 update 6 to LDOM virtual host (sun4v). I was mount NFS directory from another server in /mnt and did this steps on v240 1) I add to the /var/sadm/system/admin/.platform PLATFORM_GROUP=sun4v # cat... (1 Reply)
Discussion started by: pbubentsov
1 Replies
shutdown(1M)						  System Administration Commands					      shutdown(1M)

NAME
shutdown - shut down system, change system state SYNOPSIS
/usr/sbin/shutdown [-y] [-g grace-period] [-i init-state] [message] DESCRIPTION
shutdown is executed by the super user to change the state of the machine. In most cases, it is used to change from the multi-user state (state 2) to another state. By default, shutdown brings the system to a state where only the console has access to the operating system. This state is called single- user. Before starting to shut down daemons and killing processes, shutdown sends a warning message and, by default, a final message asking for confirmation. message is a string that is sent out following the standard warning message "The system will be shut down in ..." If the string contains more than one word, it should be contained within single (') or double (") quotation marks. The warning message and the user provided message are output when there are 7200, 3600, 1800, 1200, 600, 300, 120, 60, and 30 seconds remaining before shutdown begins. See EXAMPLES. System state definitions are: state 0 Stop the operating system. state 1 State 1 is referred to as the administrative state. In state 1 file systems required for multi-user operations are mounted, and logins requiring access to multi-user file systems can be used. When the system comes up from firmware mode into state 1, only the console is active and other multi-user (state 2) services are unavailable. Note that not all user processes are stopped when transitioning from multi-user state to state 1. state s, S State s (or S) is referred to as the single-user state. All user processes are stopped on transitions to this state. In the single-user state, file systems required for multi-user logins are unmounted and the system can only be accessed through the console. Logins requiring access to multi-user file systems cannot be used. state 5 Shut the machine down so that it is safe to remove the power. Have the machine remove power, if possible. The rc0 procedure is called to perform this task. state 6 Stop the operating system and reboot to the state defined by the initdefault entry in /etc/inittab. The rc6 procedure is called to perform this task. OPTIONS
-y Pre-answer the confirmation question so the command can be run without user intervention. -g grace-period Allow the super user to change the number of seconds from the 60-second default. -i init-state If there are warnings, init-state specifies the state init is to be in. By default, system state `s' is used. EXAMPLES
Example 1 Using shutdown In the following example, shutdown is being executed on host foo and is scheduled in 120 seconds. The warning message is output 2 minutes, 1 minute, and 30 seconds before the final confirmation message. example# shutdown -i S -g 120 "===== disk replacement =====" Shutdown started. Tue Jun 7 14:51:40 PDT 1994 Broadcast Message from root (pts/1) on foo Tue Jun 7 14:51:41... The system will be shut down in 2 minutes ===== disk replacement ===== Broadcast Message from root (pts/1) on foo Tue Jun 7 14:52:41... The system will be shut down in 1 minutes ===== disk replacement ===== Broadcast Message from root (pts/1) on foo Tue Jun 7 14:53:41... The system will be shut down in 30 seconds ===== disk replacement ===== Do you want to continue? (y or n): FILES
/etc/inittab controls process dispatching by init ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
boot(1M), halt(1M), init(1M), killall(1M), reboot(1M), ufsdump(1M), init.d(4), inittab(4), nologin(4), attributes(5) NOTES
When a system transitions down to the S or s state, the /etc/nologin file (see nologin(4)) is created. Upon subsequent transition to state 2 (multi-user state), this file is removed by a script in the /etc/rc2.d directory. SunOS 5.11 9 May 2001 shutdown(1M)
All times are GMT -4. The time now is 03:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy