02-17-2008
run level
hello
i've typed who -r command on aix 5.3 box and no answer
how do i know on what run level my machine P570 is running?
thanks
ariec
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello
I've been working on AIX 5.3 ML3 on IBM pSeries520. That server has 6 HDD drives in 3 volume groups (1+mirror in each group). I must check which phisical disk is which disk in the system. For ex. I want to know that disk in 4th slot in the machine is marked as hdisk5 on AIX. Does anybody... (2 Replies)
Discussion started by: piooooter
2 Replies
2. HP-UX
Does anyone has a CBT diskett on HPUX admin that you want to donate or sell for $50. I"m a newby admin in need of assistant... thanks..all :( (0 Replies)
Discussion started by: hpux2006
0 Replies
3. AIX
This may sound like an absolute rookie question, and it is.
I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards.
Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch.
Can someone... (1 Reply)
Discussion started by: ronellevan
1 Replies
4. AIX
We run two p5 nodes running AIX 5L in a cluster mode (HACMP), both the nodes share external disk arrays. Only the primary node can access the shared disks at a given point of time.
We are in the process of adding two new disks to the disk arrays so as to make them available to the existing... (3 Replies)
Discussion started by: dnicky
3 Replies
5. AIX
Hi I am new to AIX and any help regarding the same would be really appriciated, thanks In advance.
My priority issue is how to detect from command line that the volume / disk on AIX machine is a USB or removable disk /volume
and if possible can we list out details for that disk / volume (1 Reply)
Discussion started by: mak_mailbox
1 Replies
6. Fedora
Hi guys
I have a SSL server that is running Fedora 9. I wanted to create a directory but get:
mkdir: cannot create directory `test': Read-only file system
Any ideas? (4 Replies)
Discussion started by: wbdevilliers
4 Replies
7. Solaris
Hello to all,
what is the command in Solaris/Unix which I can use to determine how many hard disks exist in the system?
I have tried with different command such as df -lk and similar but cannot know for sure how many actual disks are installed.
Commands like # fdisk -l | grep Disk and #... (14 Replies)
Discussion started by: Mick
14 Replies
8. AIX
I have a AIX 7.1 system that has 3 failed disks, 1 in rootvg and 2 in vg_usr1.
Here is the output of lspv.
# lspv
hdisk0 00044d4dfbb11575 vg_usr1 active
hdisk1 0000150179158027 vg_usr1 active
hdisk2 ... (11 Replies)
Discussion started by: c3rb3rus
11 Replies
9. AIX
Hello
I recently received a request to reclaim hard disks and IP addresses within an AIX system(s). THe file systems are no longer in use and the client has indicated that it is OK to remove them and reclaim the disks and release the IP's. Now, since the file systems belong to a Volume group I... (8 Replies)
Discussion started by: Joseph Sabo
8 Replies
10. Shell Programming and Scripting
Hi
What I'm trying to do(manually) is logging into the server
and running the below mentioned commands
ls /sys/class/scsi_device/ | while read i; do echo "- - -" > /sys/class/scsi_device/$i/device/rescan;done
lsblk
echo -e "o\nn\np\n1\n\n\nw" | fdisk /dev/sdd
partx -a /dev/sdd1... (7 Replies)
Discussion started by: James0806
7 Replies
LEARN ABOUT POSIX
drv_usecwait
drv_usecwait(9F) Kernel Functions for Drivers drv_usecwait(9F)
NAME
drv_usecwait - busy-wait for specified interval
SYNOPSIS
#include <sys/types.h>
#include <sys/ddi.h>
void drv_usecwait(clock_t microsecs);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI).
PARAMETERS
microsecs The number of microseconds to busy-wait.
DESCRIPTION
drv_usecwait() gives drivers a means of busy-waiting for a specified microsecond count. The amount of time spent busy-waiting may be
greater than the microsecond count but will minimally be the number of microseconds specified.
delay(9F) can be used by a driver to delay for a specified number of system ticks, but it has two limitations. First, the granularity of
the wait time is limited to one clock tick, which may be more time than is needed for the delay. Second, delay(9F) may only be invoked
from user context and hence cannot be used at interrupt time or system initialization.
Often, drivers need to delay for only a few microseconds, waiting for a write to a device register to be picked up by the device. In this
case, even in user context, delay(9F) produces too long a wait period.
CONTEXT
drv_usecwait() can be called from user or interrupt context.
SEE ALSO
delay(9F), timeout(9F), untimeout(9F)
Writing Device Drivers
NOTES
The driver wastes processor time by making this call since drv_usecwait() does not block but simply busy-waits. The driver should only make
calls to drv_usecwait() as needed, and only for as much time as needed. drv_usecwait() does not mask out interrupts.
SunOS 5.10 12 Nov 1992 drv_usecwait(9F)