Sponsored Content
Full Discussion: finding hardware settings
Top Forums UNIX for Dummies Questions & Answers finding hardware settings Post 16144 by guest100 on Tuesday 26th of February 2002 06:16:23 AM
Old 02-26-2002
Try the commands above, you can grep for cache in some of them.
Or graphically use proccess management.

Cheers
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

setting constant hardware settings

Let me give a little background on the problem. I am trying to hook up a unix box through a KVM to a display. The KVM is connected to a windows box as well. When I run the mouse and monitor directly to the unix box it works pretty well. However when I trie to load it through the KVM the keyboard... (0 Replies)
Discussion started by: Winzernotman
0 Replies

2. Shell Programming and Scripting

finding duplicate files by size and finding pattern matching and its count

Hi, I have a challenging task,in which i have to find the duplicate files by its name and size,then i need to take anyone of the file.Then i need to open the file and find for more than one pattern and count of that pattern. Note:These are the samples of two files,but i can have more... (2 Replies)
Discussion started by: jerome Sukumar
2 Replies

3. Solaris

problem in finding a hardware problem

Hi I am right now facing a strange hardware problem. System get booted with the following error: Fatal Error Reset CPU 0000.0000.0000.0003 AFSR 0100.0000.0000.0000 SCE AFAR 0000.07c6.0000.1000 SC Alert: Host System has Reset It happen 4 or 5 times and get the same error every time.I... (8 Replies)
Discussion started by: girish.batra
8 Replies

4. AIX

hyperlink settings

Does anyone know the hyperlink settings to look at an AIX5L box? (1 Reply)
Discussion started by: vbagwell
1 Replies

5. Linux

Ip settings

Hi, How to set ip address in linux. Regards, Guguli (1 Reply)
Discussion started by: guguli
1 Replies

6. UNIX for Advanced & Expert Users

user settings

Hello I wonder... lets say I have to set up very very restricted rights to a user that only should be able to access logfile Y in catalogue X and nothing else. Current user is going to use Putty to access current unix machine. Is it possible to set up user settings so a user is just able to... (1 Reply)
Discussion started by: mimaca
1 Replies

7. UNIX for Dummies Questions & Answers

finding hardware config - HP-UX

HP-UX B.11.23 U ia64 model: HP RX7640/4 What commands can I issue to find out quantity/type of memory and CPUs? I know what I get from Glance but want to know if there are OS commands to get same or additional information. Thanks. Lisa (4 Replies)
Discussion started by: LisaS
4 Replies

8. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies

9. UNIX for Advanced & Expert Users

Finding the hardware model name remotely

First, forgive me if this is a stupid questions that I should have asked in the non-expert forum. It seems like a hard questions to me. Is there a way to find the hardware model name from the command line on UNIX machines in general? I want to find out what kind of machines are running at a... (5 Replies)
Discussion started by: Pug
5 Replies

10. Solaris

Solaris 11 no sound despite finding hardware

Hello Everyone, I'm new to Solaris, less than a week to give an idea how green I am.:eek: Although new to UNIX, I've been running Linux (i.e. OpenSUSE, Ultimate Edition, Arch, and obviously Ubuntu) for many years, so, I decided to put Solaris 11 on my 12 core opteron. I had a bit of difficulty... (23 Replies)
Discussion started by: Nostradamus1973
23 Replies
LOCKS(3)						   libbash locks Library Manual 						  LOCKS(3)

NAME
locks -- libbash library that implements locking (directory based). This library is not throughoutly tested - use with caution! SYNOPSIS
dirInitLock <object> [<spin>] dirTryLock <object> dirLock <object> dirUnlock <object> dirDestroyLock <object> DESCRIPTION
General locks is a collection of functions that implement locking (mutex like) in bash scripting language. The whole idea is based on the fact that directory creation/removal is an atomic process. The creation of this library was inspired by studying CVS locks management. Same lock object can by used by several processes to serialize access to some shared resource. (Well, yeah, this what locks were invented for...) To actually do this, processes just need to access lock object by the same name. Functions list: dirInitLock Initialize a lock object for your proccess dirTryLock Try to lock the lock object - give up if its already locked dirLock Lock the lock object - will block until object is unlocked dirUnlock Unlock the lock object dirDestroyLock Destroy the lock object - free resources Detailed interface description follows. FUNCTIONS DESCRIPTIONS
dirInitLock <object> [<spin>] Initialize a lock object for your process. Only after a lock is initialized, your proccess will be able to use it. Notice: This action does not lock the object. The lock can be set on two types of objects. The first is an existing directory. In this case, Aq dir must be a path (relative or full). The path must contain a '/'. The second is an abstract object used as a lock. In this case, the name of the lock will not contain any '/'. This can be used to create locks without creating real directories for them. Notice: Do not call your lock object '.lock'. Parameters: <object> The name of the lock object (either existing directory or abstract name) <spin> The time (in seconds) that the funtion dirLock will wait between two runs of dirTryLock. This parameter is optional, and its value gen- erally should be less then 1. If ommited, a default value (0.01) is set. Return Value: One of the following: 0 The action finished successfully. 1 The action failed. You do not have permissions to preform it. 3 The directory path could not be resolved. Possibly parameter does contain '/', but refers to directory that does not exist. dirTryLock <object> Try to lock the lock object. The function always returns immediately. Parameters: <object> The object that the lock is set on. Return Value: One of the following: 0 The action finished successfully. 1 The action failed. The object is already locked. 2 The action failed. Your proccess did not initialize a lock for the object. 3 The directory path could not be resolved. dirLock <object> Lock given lock object. If the object is already locked - the function will block untill the object is unlocked. After each try (dirTry- Lock) the function will sleep for spin seconds (spin is defined using dirInitLock ). Parameters: <object> The directory that the lock is set on. Return Value: One of the following: 0 The action finished successfully. 2 The action failed. Your proccess did not initialize a lock for the directory. 3 The directory path could not be resolved. dirUnlock <dir> Unlock the lock object. Parameters: <object> The object that the lock is set on. Return Value: One of the following: 0 The action finished successfully. 2 The action failed. Your proccess did not initialize the lock. 3 The directory path could not be resolved. dirDestroyLock <object> Destroys the lock object. After this action the proccess will no longer be able to use the lock object. To use the object after this action is done, one must initialize the lock, using dirInitLock. Parameters: <object> The directory that the lock is set on. Return Value: One of the following: 0 The action finished successfully. 1 The action failed. The directory is locked by your own proccess. Unlock it first. 2 The action failed. Your proccess did not initialize the lock. 3 The directory path could not be resolved. EXAMPLES
Creating an abstract lock named mylock, with 0.1 second spintime: $ dirInitLock mylock 0.1 # $?=0 Locking it: $ dirLock mylock # $?=0 Trying once to lock it again: $ dirTryLock mylock # $?=1 Trying to lock it again: $ dirLock mylock # Will wait forever Unlocking: $ dirUnlock mylock # $?=0 Destroying the lock: $ dirDestroyLock mylock # $?=0 Trying to lock again: $ dirLock mylock # $?=2 Creating a lock on the directory ./mydir, with default spin time: $ dirInitLock ./mydir # $?=0 AUTHORS
Hai Zaar <haizaar@haizaar.com> Gil Ran <gil@ran4.net> SEE ALSO
ldbash(1), libbash(1) Linux Epoch Linux
All times are GMT -4. The time now is 09:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy