03-14-2008
Hello All,
Fortunately in the system that I'm working on, I know all the scripts that are scheduled using the various scheduler apps, or are manually executed, so I know all the "starting points". None of the scripts of my concern get executed from the application code or called dynamically.
Shawn - I agree what you worte, this can be done automatially, but I just didn't want to modify a huge number of scripts for getting this information.
Under the circumstances, the solution I have opted for is a hybrid one (its not the only solution, and it may not be the best one) , composed of :
1. "trace", as I wrote in one of my earlier post - command:
trace -h -a -d -k $IGNORE -o /tmp/my_trace_log; trcon; SCRIPT_NAME ; trcoff; trcstop
and make the report by
trcrpt -O "exec=on,pid=on,timestamp=3" /tmp/my_trace_log > my_trace_log.rpt
$IGNORE practically contain ALL the categories mentioned in trchkid.h (see man page of trace) except those of FORK and EXEC. A lot of EXECs need to be grepped out from the final report, and I have what I'm looking for!
2. Another combination of solutions suggested above - I have certain scripts that I need to move from one directory to another and thus see what other scripts will be impacted due to hardcoded paths, so I wrote a fancy grepp to look through the whole filesystem limiting the searched files to "ascii text" files and "*Scripts*" (using command "file"). Sucked the life out of the box!
I have been able to pull out the information I required using the above approach.
I would like to emphasise that this solution may or may not work for all, and is certainly not covering all the scenarios. It does work for me, so I'm sharing it for everyone who took time to think about this problem.
Once again, thanks all!
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
how to find all the processes associated with a given process in unix,is there any command for this. (3 Replies)
Discussion started by: laddu
3 Replies
2. Solaris
Hi all
am new to solaris ............
i installed amanda client pkg that time am getting lots of dependency problem..........
is there any Yum server like things in solaris
Regards '
prAn (8 Replies)
Discussion started by: pran
8 Replies
3. Shell Programming and Scripting
Hello gurus,
I have three korn shell script 3.1, 3.2, 3.3. I would like to call three shell script in one shell script.
i m looking for something like this
call 3.1;
If 3.1 = "complete" then
call 3.2;
if 3.2 = ''COMPlete" then
call 3.3;
else
exit
The... (1 Reply)
Discussion started by: shashi369
1 Replies
4. Infrastructure Monitoring
Hi,
I want to install net-snmp-devel package but i have following dependecy problem.
It's very odd, i don't get it. One of packages is depended on the other one, the other one is depended on the previous one as well. :S :S
Could you help me please?
Here are the steps:
# ls -l
total... (4 Replies)
Discussion started by: oduth
4 Replies
5. Post Here to Contact Site Administrators and Moderators
First of all, I want to thank everyone who runs this forum for the fine job they've done. While I myself have not yet had any need for help, I have enjoyed and learned while helping others.
Due diligence disclaimer: I searched for a discussion on this issue, using "tynt" and "copy paste", but... (11 Replies)
Discussion started by: alister
11 Replies
6. Programming
Hello,
I'm creating an add-on for a large piece of software written in Fortran. In my directory I reference subroutines in other directories, which in turn reference more subroutines.
I'm running into trouble because on occasion the developers of the main software change some sub calls.
... (2 Replies)
Discussion started by: kudude
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I had a make file, something like that,
all:
cd dir1; make
cd dir2; make
the problem is the makefile under dir2 need some objs from dir1, so I need to set some dependency let dir2 run only after the dir1 run is done.
how to set the dependency?
Thanks.
peter (2 Replies)
Discussion started by: laopi
2 Replies
8. HP-UX
I'm building on a HP-UX ia64 system. During building, I'm getting an error
ld: Can't find dependent library "libnnz10.so"
Nowhere in my makefile do I link with this library. This library is there in the directory /databases/oracle10.2.0_64BIT/lib. I'm having two source files ora8ibulk.cpp... (1 Reply)
Discussion started by: old_as_a_fossil
1 Replies
9. Shell Programming and Scripting
Gurus,
I came across a typical requirement where the input is like-
TRANS FIRM
DEPT CUST
TRANS CUST
TRANS DEPT
FIRM CUST
& the expected Output is-
CUST
DEPT
FIRM
TRANS
This is basically a dependency list for processing the tables where
FIRM is feeding data to TRANS... (3 Replies)
Discussion started by: kapeeljoshi
3 Replies
init.d(4) init.d(4)
NAME
init.d - initialization and termination scripts for changing init states
SYNOPSIS
/etc/init.d
/etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appro-
priate to files in the rc?.d directories, where `?' is a single character corresponding to the init state. See init(1M) for definitions of
the states.
The service management facility (see smf(5)) is the preferred mechanism for service initiation and termination. The init.d and rc?.d direc-
tories are obsolete, and are provided for compatibility purposes only. Applications launched from these directories by svc.startd(1M) are
incomplete services, and will not be restarted on failure.
File names in rc?.d directories are of the form [SK]nn<init.d filename>, where S means start this job, K means kill this job, and nn is the
relative sequence number for killing or starting the job.
When entering a state (init S,0,2,3,etc.) the rc[S0-6] script executes those scripts in /etc/rc[S0-6].d that are prefixed with K followed
by those scripts prefixed with S. When executing each script in one of the /etc/rc[S0-6] directories, the /sbin/rc[S0-6] script passes a
single argument. It passes the argument 'stop' for scripts prefixed with K and the argument 'start' for scripts prefixed with S. There is
no harm in applying the same sequence number to multiple scripts. In this case the order of execution is deterministic but unspecified.
Guidelines for selecting sequence numbers are provided in README files located in the directory associated with that target state. For
example, /etc/rc[S0-6].d/README. Absence of a README file indicates that there are currently no established guidelines.
Do not put /etc/init.d in your $PATH. Having this directory in your $PATH can cause unexpected behavior. The programs in /etc/init.d are
associated with init state changes and, under normal circumstances, are not intended to be invoked from a command line.
Example 1: Example of /sbin/rc2.
When changing to init state 2 (multi-user mode, network resources not exported), /sbin/rc2 is initiated by the svc.startd(1M) process. The
following steps are performed by /sbin/rc2.
1. In the directory /etc/rc2.d are files used to stop processes that should not be running in state 2. The filenames are prefixed with K.
Each K file in the directory is executed (by /sbin/rc2) in alphanumeric order when the system enters init state 2. See example below.
2. Also in the rc2.d directory are files used to start processes that should be running in state 2. As in Step 1, each S file is executed.
Assume the file /etc/init.d/netdaemon is a script that will initiate networking daemons when given the argument 'start', and will terminate
the daemons if given the argument 'stop'. It is linked to /etc/rc2.d/S68netdaemon, and to /etc/rc0.d/K67netdaemon. The file is executed by
/etc/rc2.d/S68netdaemon start when init state 2 is entered and by /etc/rc0.d/K67netdaemon stop when shutting the system down.
svcs(1), init(1M), svc.startd(1M), svccfg(1M), smf(5)
Solaris now provides an expanded mechanism, which includes automated restart, for applications historically started via the init script
mechanism. The Service Management Facility (introduced in smf(5)) is the preferred delivery mechanism for persistently running applica-
tions. Existing init.d scripts will, however, continue to be executed according to the rules in this manual page. The details of execution
in relation to managed services are available in svc.startd(1M).
On earlier Solaris releases, a script named with a suffix of '.sh' would be sourced, allowing scripts to modify the environment of other
scripts executed later. This behavior is no longer supported; for altering the environment in which services are run, see the setenv sub-
command in svccfg(1M).
/sbin/rc2 has references to the obsolescent rc.d directory. These references are for compatibility with old INSTALL scripts. New INSTALL
scripts should use the init.d directory for related executables. The same is true for the shutdown.d directory.
17 Aug 2005 init.d(4)