02-08-2009
Sorry Dude unable to get what u exactly want to know :-)
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi ,
I am trying to ftp a file once using ascii mode and once binary mode
The ftp prompt shows different bytes transferred for each of them but at the destination server,each one of these files gets created with the same byte size and are identical.Can anyone shed any light on this
... (1 Reply)
Discussion started by: smehra
1 Replies
2. SCO
I am unbale to uncompress a file which was compress then moved to another pc in ascii mode instead of binary mode. Is there any way to recover it. Please help us. While uncompress it is giving corrupt input. (3 Replies)
Discussion started by: raj2610
3 Replies
3. UNIX for Advanced & Expert Users
Dear All,
Business Users are transfering ( FTP ) a CSV file into the IBM AIX box with transfer mode as ASCII. But I want to convert the CSV file from ASCII mode into binary mode, as my script expects file in binary mode.
Is it possible to do through Unix commands?
Thanks in Advance,
RK (1 Reply)
Discussion started by: srajeshmca
1 Replies
4. Shell Programming and Scripting
Hi
Copying a file from Unix (Solaris) to a windows server using sftp. File arrives with carriage returns and line feeds screwed (binary file transfer). Is there a way to get these to copy properly without having to edit or messa about with the file on the windows side. I know with FTP you can... (4 Replies)
Discussion started by: billy_mega
4 Replies
5. Shell Programming and Scripting
Hey Everyone!
I have searched around for this on Unix.com and Google, and I'm either not phrasing my search properly or this is not as simple as I thought...
I have a script that runs on a nightly basis that pulls one field worth of data from an internal MySQL database and populates to an... (2 Replies)
Discussion started by: Gecko12332
2 Replies
6. Shell Programming and Scripting
Hello,
When i run a bash script on ubuntu i get this message..
#!/bin/bash cannot find file or directory...
Can anibody help me with this, because the file actually exists....
Is there any extra configuration to be made? (5 Replies)
Discussion started by: oliveiraum
5 Replies
7. Shell Programming and Scripting
I am relatively new to this forum and Unix scripting.
ksh script:
part 1 :will call a PL\SQL program will create 3 CSV file at the unix directory.
part 2 : will sftp the files to the EFT server.
Once the EFT server receives these file , it will transfer them to a shared windows folders.
... (3 Replies)
Discussion started by: developerpa
3 Replies
8. Solaris
Hi,
I am getting below error in Solaris 10 SPARC when trying to issue a search on /var/tmp partition
Below is the query
/bin/find /var/tmp/ -type f -atime +1
Below is the result
/bin/find: stat() error <File> : No such file or directory (28 Replies)
Discussion started by: prash358
28 Replies
9. Shell Programming and Scripting
I am doing FTP from a server and getting below ERROR:WARNING! 16126 bare linefeeds received in ASCII mode
File may not have transferred correctly.
I looked into web and found that I may need to change the mode to binary, but when I do so the records are not in readable format...So need the file... (10 Replies)
Discussion started by: joshilalit2004
10 Replies
10. HP-UX
is there a way for my C++ application to find out which mode the hpux OS is running in?
standard mode or trusted mode. (3 Replies)
Discussion started by: einsteinBrain
3 Replies
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)