01-23-2020
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I need to find out a particular pattern from a directory, for example say X.
The X directory contains 10 c files, and it has subdirectory called Y, and Y has 20 c files within it.
Now I have to find out the pattern only from parent directory X not from sub directory Y.
I have... (4 Replies)
Discussion started by: sarwan
4 Replies
2. Shell Programming and Scripting
I have some patterns that I need to match with the content of several files and I'm having trouble to do it
Here is what I tried already :
ksh won't even execute this
#!/bin/ksh
path="/export/home/ipomwbas"
pattern=$path"/flags"
find . -name "*.properties" |\
while read file; do
... (7 Replies)
Discussion started by: flame_eagle
7 Replies
3. UNIX for Dummies Questions & Answers
Hey, I have a question about using grep and find together to locate all C programs in a directory containing certain words and open the vi editor with each file. I'm not sure how to do this in one command (as in one line). I know find has a "-exec" option that can call vi, but how do you combine... (1 Reply)
Discussion started by: MEllis5
1 Replies
4. UNIX for Dummies Questions & Answers
HI
what is the difference between find and grep
if I want to find all the files from different directories which contain "ORA" error, and the line number in each file which has ORA error
should I use pipeline ?
thanks
James (3 Replies)
Discussion started by: james94538
3 Replies
5. Shell Programming and Scripting
Hey,
I have a Find command like:
find $searchDir -type f
and this returns a list of files under the directory, which is all good, but, I want to filter that search for files that contain the string "people"
I tried something like:
find $searchDir -type f -exec grep "people" '{}'... (2 Replies)
Discussion started by: beefeater267
2 Replies
6. UNIX for Dummies Questions & Answers
:wall:Hello, Im having trouble using the find and grep combined into one command. I have the following:
find filname* -mmin -60 grep "ERROR" filename
I want to find the "ERROR" text in any file created in the last hour in the current directory. I dont know how to end the command. If I leave... (3 Replies)
Discussion started by: aispg8
3 Replies
7. UNIX for Dummies Questions & Answers
I have a file called 'test.txt' that contains alphanumeric charecters.
The file contains the word 'SBE' followed by other alphabets many times. For example, the file will contain: SBE334GH and also will have SBE77Y8I.
When i do grep 'SBE*' test.txt - it outputs the entire file.
Can you... (5 Replies)
Discussion started by: DallasT
5 Replies
8. Shell Programming and Scripting
Hi all ,
I'm new to unix
I have a checked project , there exists a file called xxx.config .
now my task is to find all the files in the checked out project which references to this xxx.config file.
how do i use grep or find command . (2 Replies)
Discussion started by: Gangam
2 Replies
9. UNIX for Dummies Questions & Answers
How can I recursively find all files in a directory and print out the file and first line number of any text blocks that match the below cases?
This would seem to involve find, xargs, *grep, regex, etc.
In summary, I want to find so-called empty "try-catch blocks" that do not contain code... (0 Replies)
Discussion started by: lifechamp
0 Replies
10. Shell Programming and Scripting
Is it possible with find and Grep to search files under a directory and display only files that have multiple occurrence of a string (In AIX)? Anybody has an example code? If not what are the other options?
Thanks in advance. (7 Replies)
Discussion started by: J_ang
7 Replies
LEARN ABOUT FREEBSD
sem_close
SEM_OPEN(3) BSD Library Functions Manual SEM_OPEN(3)
NAME
sem_open, sem_close, sem_unlink -- named semaphore operations
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <semaphore.h>
sem_t *
sem_open(const char *name, int oflag, ...);
int
sem_close(sem_t *sem);
int
sem_unlink(const char *name);
DESCRIPTION
The sem_open() function creates or opens the named semaphore specified by name. The returned semaphore may be used in subsequent calls to
sem_getvalue(3), sem_wait(3), sem_trywait(3), sem_post(3), and sem_close().
This implementation places strict requirements on the value of name: it must begin with a slash ('/') and contain no other slash characters.
The following bits may be set in the oflag argument:
O_CREAT Create the semaphore if it does not already exist.
The third argument to the call to sem_open() must be of type mode_t and specifies the mode for the semaphore. Only the S_IWUSR,
S_IWGRP, and S_IWOTH bits are examined; it is not possible to grant only ``read'' permission on a semaphore. The mode is modified
according to the process's file creation mask; see umask(2).
The fourth argument must be an unsigned int and specifies the initial value for the semaphore, and must be no greater than
SEM_VALUE_MAX.
O_EXCL Create the semaphore if it does not exist. If the semaphore already exists, sem_open() will fail. This flag is ignored unless
O_CREAT is also specified.
The sem_close() function closes a named semaphore that was opened by a call to sem_open().
The sem_unlink() function removes the semaphore named name. Resources allocated to the semaphore are only deallocated when all processes
that have the semaphore open close it.
RETURN VALUES
If successful, the sem_open() function returns the address of the opened semaphore. If the same name argument is given to multiple calls to
sem_open() by the same process without an intervening call to sem_close(), the same address is returned each time. If the semaphore cannot
be opened, sem_open() returns SEM_FAILED and the global variable errno is set to indicate the error.
The sem_close() and sem_unlink() functions return the value 0 if successful; otherwise the value -1 is returned and the global variable errno
is set to indicate the error.
ERRORS
The sem_open() function will fail if:
[EACCES] The semaphore exists and the permissions specified by oflag at the time it was created deny access to this process.
[EACCES] The semaphore does not exist, but permission to create it is denied.
[EEXIST] O_CREAT and O_EXCL are set but the semaphore already exists.
[EINTR] The call was interrupted by a signal.
[EINVAL] The sem_open() operation is not supported for the given name.
[EINVAL] The value argument is greater than SEM_VALUE_MAX.
[ENAMETOOLONG] The name argument is too long.
[ENFILE] The system limit on semaphores has been reached.
[ENOENT] O_CREAT is not set but the named semaphore does not exist.
[ENOSPC] There is not enough space to create the semaphore.
The sem_close() function will fail if:
[EINVAL] The sem argument is not a valid semaphore.
The sem_unlink() function will fail if:
[EACCES] Permission is denied to unlink the semaphore.
[ENAMETOOLONG] The specified name is too long.
[ENOENT] The named semaphore does not exist.
SEE ALSO
close(2), open(2), umask(2), unlink(2), sem_getvalue(3), sem_post(3), sem_trywait(3), sem_wait(3)
STANDARDS
The sem_open(), sem_close(), and sem_unlink() functions conform to ISO/IEC 9945-1:1996 (``POSIX.1'').
HISTORY
Support for named semaphores first appeared in FreeBSD 5.0.
BSD
January 9, 2010 BSD