Sponsored Content
Full Discussion: lsdev
Top Forums Shell Programming and Scripting lsdev Post 302215431 by Franklin52 on Wednesday 16th of July 2008 09:47:22 AM
Old 07-16-2008
An alternative for lsdev is to get the information from /proc/devices.
To use lspci you have to install the package "pciutils".

Regards
 

3 More Discussions You Might Find Interesting

1. AIX

bindprocessor and lsdev

hello I don't understand the difference between bindprocessor -q and lsdev -Cc processor When i use the first, i have 8 processors, but when i use the second, i have 4 processors ? thank you for your help, (0 Replies)
Discussion started by: pascalbout
0 Replies

2. UNIX for Dummies Questions & Answers

Dynix/ptx equivalents of lsdev, mkdev etc.

I am familiar with the AIX commands lsdev, mkdev, rmdev and so on. Have been asked to look at a very old Sequent Quad box running Dynix/ptx - believed to be version 2.4.1 ! These commands don't appear to be present. Can anyone please identify the equivalent Dynix commands? I've been handed the... (0 Replies)
Discussion started by: itboss
0 Replies

3. AIX

lsdev -Cc and location info

Hi, I try to understand what means the following location code I can get with the following command : lsdev -Cc tape rmt0 Available 05-08-02 IBM 3580 Ultrium Tape Drive (FCP) rmt1 Available 05-08-02 IBM 3580 Ultrium Tape Drive (FCP) I can find info for 05-08, means RMT0/1 are... (1 Reply)
Discussion started by: unclefab
1 Replies
FLOCK(1)							   User Commands							  FLOCK(1)

NAME
flock - manage locks from shell scripts SYNOPSIS
flock [-sxon] [-w timeout] lockfile [-c] command... flock [-sxon] [-w timeout] lockdir [-c] command... flock [-sxun] [-w timeout] fd DESCRIPTION
This utility manages flock(2) locks from within shell scripts or the command line. The first and second forms wraps the lock around the executing a command, in a manner similar to su(1) or newgrp(1). It locks a specified file or directory, which is created (assuming appropriate permissions), if it does not already exist. The third form is convenient inside shell scripts, and is usually used the following manner: ( flock -n 9 || exit 1 # ... commands executed under lock ... ) 9>/var/lock/mylockfile The mode used to open the file doesn't matter to flock; using > or >> allows the lockfile to be created if it does not already exist, how- ever, write permission is required; using < requires that the file already exists but only read permission is required. By default, if the lock cannot be immediately acquired, flock waits until the lock is available. OPTIONS
-s, --shared Obtain a shared lock, sometimes called a read lock. -x, -e, --exclusive Obtain an exclusive lock, sometimes called a write lock. This is the default. -u, --unlock Drop a lock. This is usually not required, since a lock is automatically dropped when the file is closed. However, it may be required in special cases, for example if the enclosed command group may have forked a background process which should not be hold- ing the lock. -n, --nb, --nonblock Fail (with an exit code of 1) rather than wait if the lock cannot be immediately acquired. -w, --wait, --timeout seconds Fail (with an exit code of 1) if the lock cannot be acquired within seconds seconds. Decimal fractional values are allowed. -o, --close Close the file descriptor on which the lock is held before executing command. This is useful if command spawns a child process which should not be holding the lock. -c, --command command Pass a single command to the shell with -c. -h, --help Print a help message. AUTHOR
Written by H. Peter Anvin <hpa@zytor.com>. COPYRIGHT
Copyright (C) 2003-2006 H. Peter Anvin. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. SEE ALSO
flock(2) AVAILABILITY
The flock command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. util-linux February 2006 FLOCK(1)
All times are GMT -4. The time now is 07:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy