09-16-2010
unable to find any related post
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
writing a script that will check every 5 seconds whether a particular user has
logged into the system
# Determine if someone is logged on
# Version 4.0
if
then
echo “ Incorrect number of arguments”
echo “Usage: $ ison4 <user>”
else
user=“$1”
if who | grep “$user” > /dev/null
then... (2 Replies)
Discussion started by: kim187
2 Replies
2. Shell Programming and Scripting
Hello,
i know who command gives you the time when particular user logged in. And subtracting today's date and time from the one found in who we can get how much time user logged in. But this can get very much clumsy as we can't subtract date directly in unix . Is there any other way or command... (4 Replies)
Discussion started by: salman4u
4 Replies
3. UNIX for Dummies Questions & Answers
Hi all..
I was trying to do a little shell script, that would list users and their login times, lets say like last 5 days.
But I couldnt figure out how to count users login times from previous days. Any tips?
Funny that nobody has do this kinda script before, or atleast I couldnt find on... (2 Replies)
Discussion started by: Kimmo_
2 Replies
4. Shell Programming and Scripting
Ok, so, in order to install some dependencies of a program I made, a script has to be run as root. The thing is that I have to copy some things into the home folder of currently logged in user, but the variable $HOME returns '/root' and the $USER returns 'root' :(
Is there any way to see who is... (7 Replies)
Discussion started by: hakermania
7 Replies
5. Shell Programming and Scripting
Hello all,
I want to display all the user logged last week and know the time tnat they are connected. I have been looking for a solution in the Forum, but I didn't find.
Thanks in advance (4 Replies)
Discussion started by: ahernandez
4 Replies
6. UNIX for Dummies Questions & Answers
Hi all
So I am thinking my inability to cope with math is bogging me down here so Im asking for help.
I want to determine how long a user has been logged on for by using the date and who commands to determine the time they have been logge don.
My problem is that I keep getting the wrong... (2 Replies)
Discussion started by: losingit
2 Replies
7. Homework & Coursework Questions
I was given this to do,
Write a Shell script to automatically check that a specified user is logged in to the computer.
The program should allow the person running the script to specify the name of the user to be checked, the frequency in seconds at which the script should check. If a... (0 Replies)
Discussion started by: operator
0 Replies
8. Shell Programming and Scripting
Hi
I have below scenario, I hope this could be possible, but as of now no idea how to implement this.
Mount point in this location /abc/mp, and there will different users who will be executing one the file shell1.sh file located in /abs/mp, but every user will execute this shell1.sh file from... (1 Reply)
Discussion started by: shekharjchandra
1 Replies
9. Shell Programming and Scripting
Hi,
I am relatively new to the cluster administration and shell scripting. I need help on a shell script which can help me determine how many cpu's over time, any particular ( or all registered users on a cluster ) are using. To generate data say over a period of week and list of users and their... (6 Replies)
Discussion started by: anuj06
6 Replies
10. Shell Programming and Scripting
help me (1 Reply)
Discussion started by: sonu pandey
1 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)