|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
Why does my test fail ??
Post 302593629 by Corona688 on Friday 27th of January 2012 03:24:46 PM
01-27-2012
|
|
6 More Discussions You Might Find Interesting
1. Solaris
Hi
I have a problem in installing solaris 9 in a ULTRA Enterprise 2 machine.
The cdrom does not keep the cd in. When I put the installtion cd 1 and close the tray, I can see the led blinks three times and then the tray comes out. I borrowed a set of installtion cd s from one of my friends (they... (3 Replies)
Discussion started by: enke1234
3 Replies
2. Shell Programming and Scripting
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
Discussion started by: Max89
1 Replies
3. Shell Programming and Scripting
How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies
4. Shell Programming and Scripting
Hi,
I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the... (5 Replies)
Discussion started by: royalibrahim
5 Replies
5. Shell Programming and Scripting
Hi Team,
I have a file named as follows: aaa.tar.gz
Now I need to verify if the untar fails, then the script has to send a mail. In order to check this condition, I need a tar.gz file which is unable to untar it. Can anyone help me to create a file which I will be able to unzip successfully... (2 Replies)
Discussion started by: kmanivan82
2 Replies
6. Forum Support Area for Unregistered Users & Account Problems
After inputted all required fields in registration page, the below message is shown and cannot go on.
A required field called Custom Date & Time Formats is missing or has an invalid value. (2 Replies)
Discussion started by: Unregistered
2 Replies
LEARN ABOUT SUSE
usoc
usoc(7D) Devices usoc(7D) NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL. FILES
/kernel/drv/usoc 32-bit ELF kernel module /kernel/drv/sparcv9/usoc 64-bit ELF kernel module ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Interface stability |Unknown | +-----------------------------+-----------------------------+ |Availability |SUNWusoc | +-----------------------------+-----------------------------+ SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D) Writing Device Drivers Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994 Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996 Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998 Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998 DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by: usoc%d: where usoc%d: is the per-port instance number of the usoc controller. Fibre Channel is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is OFFLINE The Fibre Channel loop is now offline. attach failed: device in slave-only slot. Move soc+ card to another slot. attach failed: alloc soft state. Driver did not attach, devices will be inaccessible. attach failed: bad soft state. Driver did not attach, devices will be inaccessible. attach failed: unable to map eeprom Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map XRAM Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map registers Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access status register Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to install interrupt handler Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access host adapter XRAM Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to write host adapter XRAM Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: read/write mismatch in XRAM Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. SunOS 5.10 20 Jul 1999 usoc(7D)