Sponsored Content
Full Discussion: grep in Solaris
Top Forums UNIX for Dummies Questions & Answers grep in Solaris Post 302376458 by njafri on Tuesday 1st of December 2009 11:54:13 AM
Old 12-01-2009
I am looking for smthng that will grep a process having both the strings....the command that u post ..gives rman OR MRTP...whereas i am looking for rman AND MRTP
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problems with grep on solaris 5.8

Hi all, I have a problem when i grep for a particular field among all fhe files in the directory. if i do an ls -l field * i can find it. however at the moment the number of files in the directory are close to 28000 and it returns an ksh: /usr/bin/grep: arg list too long Assuming i... (2 Replies)
Discussion started by: manualvin
2 Replies

2. Solaris

grep -e doesn't work on solaris

grep -e doesn't work in Soalris. Same script with grep -e worked on AIX/HP/LINUX.. I would like to search a list of patterns on "log.txt" like ... grep -e FATAL -e ERROR log.txt I get the error message as grep: illegal option -- e Usage: grep -hblcnsviw pattern file . . . (3 Replies)
Discussion started by: jmkraja
3 Replies

3. UNIX for Dummies Questions & Answers

How to grep word + next line in solaris 10?

Hi my unix friends, How do I grep a word and next line with solaris 10. tnx Mehrdad ---------- Post updated at 03:17 PM ---------- Previous update was at 03:09 PM ---------- I found this one: cat <file_name> | awk '/<seek_word>/ {print;getline;print}' (3 Replies)
Discussion started by: mehrdad68
3 Replies

4. Shell Programming and Scripting

Help on Grep in solaris

Hi all, I had a script which is running in HP Unix machine. Now we are migrating to Solaris i need to run the same script which is giving me errors . grep -iqf $PATTERN output.log grep -vif $PATTERN2 output2.log when i execute these in Solaris its giving me unknown option -q -f could... (7 Replies)
Discussion started by: firestar
7 Replies

5. Shell Programming and Scripting

grep -o does not work in Solaris

I am using the code below to grep through a list of files (TEMPFILE) and look for rsync, rdist, rsh, ftp, etc. in each file. Do a count of each, and output that to a logfile. This works great in Linux, but not at all in Solaris because the EGREP -o option does not exist. Anyone have an idea... (5 Replies)
Discussion started by: nitrobass24
5 Replies

6. Solaris

grep options in solaris

Hi, I am interested in knowing the grep optiojs availabel in solaris box, to get the grep results in one line from the log files. only the matched values need to be displayed. I need ot find the values in a message where the search values will be in separate lines of the input. like:... (10 Replies)
Discussion started by: sudha143
10 Replies

7. UNIX for Dummies Questions & Answers

grep issue (Solaris)

Can anyone explain this (i.e. why the 2nd grep does not find anything)?: -bash-3.00$ cat tmp.log sftp> chdir /home/test-dir sftp> mget thosefiles*.txt File "/home/test-dir/thosefiles*.txt" not found. -bash-3.00$ grep "s*.txt" tmp.log sftp> mget thosefiles*.txt File... (4 Replies)
Discussion started by: dhebden
4 Replies

8. Shell Programming and Scripting

Grep to display file name along with content in Solaris

Am using the following grep to match a particular patter in grep. grep xyz abc.txt now while i run this command, if the pattern matched, am getting the line containing xyz Output: xyz is doing some work Now if i want the file name also along with my output, what should i do Expected... (2 Replies)
Discussion started by: rituparna_gupta
2 Replies

9. Solaris

Need grep package with -A option for Solaris 10

Hi Guys, I need grep package with -A option for Solaris 10, Where can I download this from, Please advise. (2 Replies)
Discussion started by: manalisharmabe
2 Replies

10. Shell Programming and Scripting

Grep works on Linux but fails on Solaris

Hi, On linux i have the below command working fine. grep -o '<name>.*</name>' deploy.tmp | sed 's/\(<name>\|<\/name>\)//g' deploy.tmp But the same is failing on Solaris uname -a SunOS mymac 5.10 Generic_150400-23 sun4v sparc sun4v Can you tell me how can i get it work on Solaris ?... (6 Replies)
Discussion started by: mohtashims
6 Replies
RMAN(9) 						   BSD Kernel Developer's Manual						   RMAN(9)

NAME
rman, rman_activate_resource, rman_await_resource, rman_deactivate_resource, rman_fini, rman_init, rman_manage_region, rman_release_resource, rman_reserve_resource, rman_reserve_resource_bound, rman_make_alignment_flags, rman_get_start, rman_get_end, rman_get_device, rman_get_size, rman_get_flags, rman_set_virtual, rman_get_virtual, rman_set_bustag, rman_get_bustag, rman_set_bushandle, rman_get_bushandle, rman_set_rid, rman_get_rid -- resource management functions SYNOPSIS
#include <sys/rman.h> int rman_activate_resource(struct resource *r); int rman_await_resource(struct resource *r, int pri2, int timo); int rman_deactivate_resource(struct resource *r); int rman_fini(struct rman *rm); int rman_init(struct rman *rm); int rman_manage_region(struct rman *rm, u_long start, u_long end); int rman_release_resource(struct resource *r); struct resource * rman_reserve_resource(struct rman *rm, u_long start, u_long end, u_long count, u_int flags, struct device *dev); struct resource * rman_reserve_resource_bound(struct rman *rm, u_long start, u_long end, u_long count, u_long bound, u_int flags, struct device *dev); uint32_t rman_make_alignment_flags(uint32_t size); u_long rman_get_start(struct resource *r); u_long rman_get_end(struct resource *r); struct device * rman_get_device(struct resource *r); u_long rman_get_size(struct resource *r); u_int rman_get_flags(struct resource *r); void rman_set_virtual(struct resource *r, void *v); void * rman_get_virtual(struct resource *r); void rman_set_bustag(struct resource *r, bus_space_tag_t t); bus_space_tag_t rman_get_bustag(struct resource *r); void rman_set_bushandle(struct resource *r, bus_space_handle_t h); bus_space_handle_t rman_get_bushandle(struct resource *r); void rman_set_rid(struct resource *r, int rid); int rman_get_rid(struct resource *r); DESCRIPTION
The rman set of functions provides a flexible resource management abstraction. It is used extensively by the bus management code. It imple- ments the abstractions of region and resource. A region descriptor is used to manage a region; this could be memory or some other form of bus space. Each region has a set of bounds. Within these bounds, allocated segments may reside. Each segment, termed a resource, has several proper- ties which are represented by a 16-bit flag register, as follows. #define RF_ALLOCATED 0x0001 /* resource has been reserved */ #define RF_ACTIVE 0x0002 /* resource allocation has been activated */ #define RF_SHAREABLE 0x0004 /* resource permits contemporaneous sharing */ #define RF_TIMESHARE 0x0008 /* resource permits time-division sharing */ #define RF_WANTED 0x0010 /* somebody is waiting for this resource */ #define RF_FIRSTSHARE 0x0020 /* first in sharing list */ #define RF_PREFETCHABLE 0x0040 /* resource is prefetchable */ The remainder of the flag bits are used to represent the desired alignment of the resource within the region. The rman_init() function initializes the region descriptor, pointed to by the rm argument, for use with the resource management functions. It is required that the fields rm_type and rm_descr of struct rman be set before calling rman_init(). The field rm_type shall be set to RMAN_ARRAY. The field rm_descr shall be set to a string that describes the resource to be managed. It also initializes any mutexes associ- ated with the structure. If rman_init() fails to initalize the mutex, it will return ENOMEM; otherwise it will return 0 and rm will be ini- talized. The rman_fini() function frees any structures associated with the structure pointed to by the rm argument. If any of the resources within the managed region have the RF_ALLOCATED flag set, it will return EBUSY; otherwise, any mutexes associated with the structure will be released and destroyed, and the function will return 0. The rman_manage_region() function establishes the concept of a region which is under rman control. The rman argument points to the region descriptor. The start and end arguments specify the bounds of the region. If successful, rman_manage_region() will return 0. If the region overlaps with an existing region, it will return EBUSY. ENOMEM will be return when rman_manage_region() failed to allocate memory for the region. The rman_reserve_resource_bound() function is where the bulk of the rman logic is located. It attempts to reserve a contiguous range in the specified region rm for the use of the device dev. The caller can specify the start and end of an acceptable range, as well as alignment, and the code will attempt to find a free segment which fits. The start argument is the lowest acceptable starting value of the resource. The end argument is the highest acceptable ending value of the resource. Therefore, start + count - 1 must be <= end for any allocation to happen. The default behavior is to allocate an exclusive segment, unless the RF_SHAREABLE or RF_TIMESHARE flags are set, in which case a shared segment will be allocated. If this shared segment already exists, the caller has its device added to the list of consumers. The rman_reserve_resource() function is used to reserve resources within a previously established region. It is a simplified interface to rman_reserve_resource_bound() which passes 0 for the flags argument. The rman_make_alignment_flags() function returns the flag mask corresponding to the desired alignment size. This should be used when calling rman_reserve_resource_bound(). The rman_release_resource() function releases the reserved resource r. It may attempt to merge adjacent free resources. The rman_activate_resource() function marks a resource as active, by setting the RF_ACTIVE flag. If this is a time shared resource, and the caller has not yet acquired the resource, the function returns EBUSY. The rman_deactivate_resource() function marks a resource r as inactive, by clearing the RF_ACTIVE flag. If other consumers are waiting for this range, it will wakeup their threads. The rman_await_resource() function performs an asynchronous wait for a resource r to become inactive, that is, for the RF_ACTIVE flag to be cleared. It is used to enable cooperative sharing of a resource which can only be safely used by one thread at a time. The arguments pri and timo are passed to the rman_await_resource() function. The rman_get_start(), rman_get_end(), rman_get_size(), and rman_get_flags() functions return the bounds, size and flags of the previously reserved resource r. The rman_set_bustag() function associates a bus_space_tag_t t with the resource r. The rman_get_bustag() function is used to retrieve this tag once set. The rman_set_bushandle() function associates a bus_space_handle_t h with the resource r. The rman_get_bushandle() function is used to retrieve this handle once set. The rman_set_virtual() function is used to associate a kernel virtual address with a resource r. The rman_get_virtual() function can be used to retrieve the KVA once set. The rman_set_rid() function associates a resource identifier with a resource r. The rman_get_rid() function retrieves this RID. The rman_get_device() function returns a pointer to the device which reserved the resource r. SEE ALSO
bus_activate_resource(9), bus_alloc_resource(9), bus_release_resource(9), bus_set_resource(9), mutex(9) AUTHORS
This manual page was written by Bruce M Simpson <bms@spc.org>. BSD
April 29, 2007 BSD
All times are GMT -4. The time now is 11:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy