Add the following line to every single shell script (at the top, right after the shebang line, in case the script halts execution somewhere due to a conditional):
Code:
echo -e "$0\t$(date)" >> scripts.log
This way, you'll end up with a log file which will show you which scripts were executed and when. This doesn't directly address your problem of finding out which scripts call which, but you can do that with some fancy grep work. And in any case, I believe the whole point of that was to make sure you weren't leaving unused scripts out there, and this will identify all used scripts.
Note: the $0 in a bash script will be replaced with the name of the current command. If you run that from the command line (outside of a script), it will simply return "bash."
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT MOJAVE
platform::shell
platform::shell(n) Tcl Bundled Packages platform::shell(n)
__________________________________________________________________________________________________________________________________________________NAME
platform::shell - System identification support code and utilities
SYNOPSIS
package require platform::shell ?1.1.4?
platform::shell::generic shell
platform::shell::identify shell
platform::shell::platform shell
_________________________________________________________________DESCRIPTION
The platform::shell package provides several utility commands useful for the identification of the architecture of a specific Tcl shell.
This package allows the identification of the architecture of a specific Tcl shell different from the shell running the package. The only
requirement is that the other shell (identified by its path), is actually executable on the current machine.
While for most platform this means that the architecture of the interrogated shell is identical to the architecture of the running shell
this is not generally true. A counter example are all platforms which have 32 and 64 bit variants and where a 64bit system is able to run
32bit code. For these running and interrogated shell may have different 32/64 bit settings and thus different identifiers.
For applications like a code repository it is important to identify the architecture of the shell which will actually run the installed
packages, versus the architecture of the shell running the repository software.
COMMANDS
platform::shell::identify shell
This command does the same identification as platform::identify, for the specified Tcl shell, in contrast to the running shell.
platform::shell::generic shell
This command does the same identification as platform::generic, for the specified Tcl shell, in contrast to the running shell.
platform::shell::platform shell
This command returns the contents of tcl_platform(platform) for the specified Tcl shell.
KEYWORDS
operating system, cpu architecture, platform, architecture
platform::shell 1.1.4 platform::shell(n)