Sponsored Content
Top Forums UNIX for Advanced & Expert Users Immediate Help Required for Patch Installation on Solaris Post 302334900 by kamaldeep1986 on Thursday 16th of July 2009 07:41:48 PM
Old 07-16-2009
Hi

Thanks alot.
 

10 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Patch Installation

I am having trouble installing some HPUX patches on my 11.00. I am a novice at this so bear with me. I do not understand how to install depots. Now I'm trying to patch my system so I can get the Oracle client installed. Oracle says I need these two patches: PHSS_21950, QPK_11.00.64 I go to:... (0 Replies)
Discussion started by: RAFA
0 Replies

2. Solaris

patch installation

Hey hi all, I just recently encountered these question regarding patch installation, the scenario is like these that i have three patches a,b,c and each of them require a server reboot.And I don't have to reboot the server three times..i can reboot it only once.. so what should i do ? Mine... (1 Reply)
Discussion started by: sahil_shine
1 Replies

3. Solaris

Required installation steps for perl 5.8.9 on Solaris 2.8 operating system

Hi Can any one suggest me the instalation guideline for perl 5.8.9 on UNIX/solaris 2.8 environment. Pooja (2 Replies)
Discussion started by: wadhwa.pooja
2 Replies

4. Solaris

Immediate Help Required for Patch Installation on Solaris 10

Hi All, I am new to Solaris. I have to install some latest patches on my SPARC Machine running Solaris 10. I have installed the required patches. Please guide me through the rest of the process. Please include even minute details so that I don't face any problems while doing this activity. ... (0 Replies)
Discussion started by: kamaldeep1986
0 Replies

5. Solaris

Solaris patch cluster installation error

Hi Admins, I came across an error while installing patch cluster on solaris. # ./installcluster --s10cluster ERROR: Another instance of an install script is already running for target boot environment '/'. I did killed the related processes. Now there is no any process running from ps... (1 Reply)
Discussion started by: snchaudhari2
1 Replies

6. Red Hat

Patch Installation

Dear All, I have some 6 RedHat Servers ( 5.4 ) tikanga connected to the Intranet. Some are Database Servers and application servers. For the past 1.5 years , we have not installed any patches.. Is there any way to find out , whether these systems needs patches and where to... (5 Replies)
Discussion started by: jegaraman
5 Replies

7. Solaris

Patch installation

Can any one let me know the complete steps to install patch on a production server like Sun Fire V440. (7 Replies)
Discussion started by: chetansingh23
7 Replies

8. Solaris

OS Patch Installation

Hello, I'm very new to this forum and solaris - I have solaris 5.10 installed on my machine (x86) and when I did a prerequisite check for Oracle Database 11g R2, it was showing the following patches are missing - OS Patch:137104-02 OS Patch:120754-06 OS Patch:119961-05 OS Patch:119964-14... (3 Replies)
Discussion started by: dsreedharan
3 Replies

9. Linux

Patch Installation

Am new to Linux and this forum From where can I download sysstatx86_64 and numactl-devel patches ? Thanks! :b: (1 Reply)
Discussion started by: dsreedharan
1 Replies

10. Solaris

Solaris 10 flash installation - fatal error. Solaris installation program exited.

Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error. Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies
hexec(1)																  hexec(1)

NAME
hexec - a process execution hooking tool SYNOPSIS
hexec <OPTIONS> [expr] [cmd] [args...] DESCRIPTION
hexec is a tool to hook into process exececution calls (exec family of syscalls). You can define an expression that is executed against any hooked exec call. This expression may also contain a replacement exec call. OPTIONS SUMMARY
Here is a summary of the options to hexec. --help | -h Print a options/expr summary page --version | -v Print hexec version --log-out | -lo set output file for error and -print output OPTIONS
-h Print a options/expr summary page --help Print a options/expr summary page -lo Set the output file for error and -print output. This can be required if writing to stderr could cause malfunction because some processes read from stderr and expect a well defined output. EXPRESSIONS
The expression is executed against all process execution calls. If the expression returns true, the original call is skipped. <expr> -and <expr> <expr> -a <expr> <expr> <expr> Returns true if both expressions return true. If the left returns false, the right expression is never executed. <expr> -or <expr> <expr> -o <expr> Returns true if one of both expressions returns true. If the left returns true, the right expression is never executed. -path <pattern> Returns true if the path of the executable matches <pattern>. <pattern> is a bash compatible wild card pattern. -ipath <pattern> Same as -path, but case insensitive. -name <pattern> Returns true if the base name of the executable matches <pattern>. <pattern> is a bash compatible wild card pattern. -iname <pattern> Same as -name, but case insensitive. -contains <str> Returns true if the path of the executable containes the string <str>. -icontains <str> Same as -contains, but case insensitive. -print Print all arguments to the called process. Returns always true. -exec <cmd> [args...] ; Executes <cmd> with [args...] as arguments. This expression must be terminated with a semicolon. You can use argument placeholders in <cmd> and [args...] (see below). This expression always returns true. NOTE: Please be aware that you may need to escape or quote the terminating semicolon to not confuse your shell. -sh <script> Interprets <script> as a shell script by invoking /bin/sh with the arguments -c '<script>'. You can use argument placeholders inside <script>. Please note that -sh only expects a single argument and not a variable list of arguments (as -exec does). Using -sh is the same as using -exec sh -c <script>. PLACEHOLDERS FOR -exec EXPRESSION Every -exec expression can use placeholders in the argument list to obtain information from the original exec call. Each placeholder starts with { and ends with }. Use { if you want to use a { in your argument list. The placeholders are replaced when the -exec expression is evaluated. Placeholder types: {n} Will be replaced with the number of arguments in the original call. {<idx>} Will be replaced with the original argument at index <idx>. Example: {1} would give the first argument. You can prepend <idx> with placeholder flags. {} Will be replaced with all arguments from the original call. Each argument is seperated with a space. You can use placeholder flags. NOTE: The executable name is also considered as argument. This means that a call like "echo test" will result in two arguments, "echo" and "test". PLACEHOLDER FLAGS
s Every argument is inserted as single argument instead of concatenating all arguments. Consider the arguments 'a', 'b' and 'c'. Without s, -exec {} ; would result in -exec 'a b c' ;, which in many cases is not what you want. -exec {s} ; howewer would result in -exec 'a' 'b' 'c' ;. q Quote every single argument. e Escape all non alpha-numeric characters. This flag is very useful when using a "sh -c <...>" in the -exec expression. Examples -exec echo {} ; with the call 'a' 'b' 'c' results in: 'echo' 'a b c' -exec echo {q} ; with the call 'a' 'b' 'c' results in: 'echo' 'a' 'b' 'c' -exec sh -c 'echo {}; {}' ; with the call 'sh' '-c' 'gcc d.c >> log.txt' results in: 'sh' '-c' 'echo sh -c gcc d.c >> log.txt; sh -c gcc d.c >> log.txt' Please note that this will not do what you may expect, as the >> is handled wrong in this case. -exec sh -c 'echo {e}; {}' ; with the call 'sh' '-c' 'gcc d.c >> log.txt' results in: 'sh' '-c' 'echo sh -c gcc d.c >> log.txt; sh -c gcc d.c >> log.txt' CHANGES TO PROCESSES
hexec will add some environment variables to the hooked processes. These are (may not be complete): LD_PRELOAD hexec adds libhexec-hook.so to the list of preloaded libraries. HEXEC_EXPR_SHM Contains the name of the internal shared memory object. HEXEC_LOG_FD Contains the file descriptor for error and -print output. Please do never modify these environment variables. Also take care when you use these variables, because the name and content of the vari- ables may change in the future. EXAMPLES
hexec -name 'gcc' -exec ccache {s} ; make Calls make, which will then call gcc several times. The executable name of each hooked process execution is tested against the file pattern "gcc" and "ccache {s}" is called each time a match is found. '{s}' will be replaced with the original (the hooked) call. In this example, a call to "gcc -o test.o test.c" would be replaced with "ccache gcc -o test.o test.c" HOW IT WORKS
TODO BUGS
I'm sure there are alot...it's still beta :) AUTHOR
hexec was written by Alexander Block http://blocksoftware.net/ If you wish to report a problem or make a suggestion then please email ablock@blocksoftware.net hexec is released under the GNU General Public License version 2 or later. Please see the file COPYING for license details. November 2008 hexec(1)
All times are GMT -4. The time now is 06:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy