12-23-2011
Have you tried ipadm enable-if aggr0 - without "-t" and then reboot?
10 More Discussions You Might Find Interesting
1. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
2. UNIX for Advanced & Expert Users
Hey folks,
i need communicate between 2 processes in a reliable manner. The information delivery has to be guarenteed. I thought about proc 2 sending a signal to proc 1 when information has being written to disc and wirte() has been verified (sync/flush). The IPC method for the data is named... (4 Replies)
Discussion started by: heck
4 Replies
3. Shell Programming and Scripting
I found a way to make a numeric variable persistent for a script :
#!/bin/bash
function Persist() { # 1:Expression like VARIABLE=Value (numeric)
local V=${1%=*}
eval "$1"
sed -i "s/^$V=*/$1/" $(which $(basename $0)) || return 1
}And how to use itAA=12
read -p "Enter a... (2 Replies)
Discussion started by: frans
2 Replies
4. AIX
Hi,
I want to use the service IP incase for any network activity rather than the persistent IP as the Persistent IP is blacklisted in our network. Is there any way
to make the service ip as LPARs default IP to be used as the lpars source IP incase it pings anything or acceses any external... (6 Replies)
Discussion started by: aixromeo
6 Replies
5. AIX
i am trying to make HACMP but when i add a persistent ip, error shows unable to determine address for 'UPIDGIS1_pers'
pls help me out
AIX - 5.3
HACMP -5.4
thanks (2 Replies)
Discussion started by: reply.ravi
2 Replies
6. AIX
I am new in AIX and please forgive my poor english.
I know that AIX allow same subnet IPs for different interfaces, which result in multipath routing / route striping.
My question is,
is there any best practice for the persistent and service IP with same subnet to stay on same interface, or... (5 Replies)
Discussion started by: skeyeung
5 Replies
7. War Stories
:wall::wall::wall::wall:
I am sharing some techno-geeky-work related issue, which can best be dissected here only.
I am expecting more of a discussion,as serious as when two guys sharing experience over smoke and beer.
The thing is, till now i have been only a student, so never cared about how... (10 Replies)
Discussion started by: animesharma
10 Replies
8. Programming
I noticed that when attempting to download videos from the url, I receive a 403 forbidden when I get through to a certain point in my downloads. I can download a third of the videos but will error:
Retrieving file 'blah-video.f4v'...
Traceback (most recent call last): ... (0 Replies)
Discussion started by: metallica1973
0 Replies
9. AIX
I have done other clusters (HP MC/Service Guard and oracle Clusters, and RHEL Cluster services), and have good idea about hacmp (a little older knowledge).
However the term "Boot IP" for some reason is messing with my head. Have not done HACMP since the 4.1.2.X days.
Is the Bootip the... (1 Reply)
Discussion started by: mrmurdock
1 Replies
10. Solaris
Hi,
I am trying to create aggregation by using dladm, But am getting the following error.
dladm create-aggr -P L2 -l net2 sumaggr2
dladm: create operation failed: link busy
I have checked in dladm show-link and the state is "down"..
dladm show-link | grep ^net2
net2 phys ... (1 Reply)
Discussion started by: Sumanthsv
1 Replies
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, poweroff, halt -- restarting, powering down and stopping the system
SYNOPSIS
halt [-dlnpqvxz]
poweroff [-dlnqvxz]
reboot [-dlnqvxz] [arg ...]
DESCRIPTION
The poweroff, halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM, wait for up to 30 seconds
for them to die, send a SIGKILL to the survivors and, respectively, power down, halt or restart the system. The action is logged, including
entering a shutdown record into the login accounting file and sending a message via syslog(3).
The options are as follows:
-d Create a dump before halting or restarting. This option is useful for debugging system dump procedures or capturing the state of a
corrupted or misbehaving system.
-l Suppress sending a message via syslog(3) before halting or restarting.
-n Do not flush the file system cache. This option should be used with extreme caution. It can be used if a disk or a processor is on
fire.
-p Attempt to powerdown the system. If the powerdown fails, or the system does not support software powerdown, the system will halt.
This option is only valid for halt.
-v To enable verbose messages on the console, pass the boothowto(9) flag AB_VERBOSE to reboot(2).
-x To enable debugging messages on the console, pass the boothowto(9) flag AB_DEBUG to reboot(2).
-z To silence some shutdown messages on the console, pass the boothowto(9) flag AB_SILENT to reboot(2).
-q Do not give processes a chance to shut down before halting or restarting. This option should not normally be used.
If there are any arguments passed to reboot they are concatenated with spaces and passed as bootstr to the reboot(2) system call. The string
is passed to the firmware on platforms that support it.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom.
SEE ALSO
reboot(2), syslog(3), utmp(5), boot(8), init(8), rescue(8), shutdown(8), sync(8)
HISTORY
A reboot command appeared in Version 6 AT&T UNIX.
The poweroff command first appeared in NetBSD 1.5.
CAVEATS
Once the command has begun its work, stopping it before it completes will probably result in a system so crippled it must be physically
reset. To prevent premature termination, the command blocks many signals early in its execution. However, nothing can defend against delib-
erate attempts to evade this.
This command will stop the system without running any shutdown(8) scripts. Amongst other things, this means that swapping will not be dis-
abled so that raid(4) can shutdown cleanly. You should normally use shutdown(8) unless you are running in single user mode.
BUGS
The single user shell will ignore the SIGTERM signal. To avoid waiting for the timeout when rebooting or halting from the single user shell,
you have to exec reboot or exec halt.
BSD
February 16, 2011 BSD