Solaris

Solaris 9 is old (released in 2002, supported until 2014), but is not ancient. The "ls" command hasn't substantially changed in the last 3 or 4 four decades so identifying the scripts that have been accessed is a first and easy step. Same for accounting which was supported by Solaris 9.

Anyway, a simple method to identify if existing scripts are executed is to wrap them with a logger script.

For example, assuming you have several shell scripts in the /opt/local/bin directory

You create a directory /opt/local/bin_org and move the scripts you want to monitor in it, then you create a wrapper script and have the system using it when the original scripts are expected:

Code:

cd /opt/local/bin/
cat > .wrapper <<%
#!/bin/ksh
echo \$0 "\$@" called at \$(PATH=$(getconf PATH) date +%Y%m%dT%H%M%S) >> /var/tmp/scriptLogs
exec \$(PATH=$(getconf PATH) dirname \$0)/../bin_org/\$(PATH=$(getconf PATH) basename \$0) "\$@"
%
chmod +x .wrapper
for script in ../bin_org/*; do
    ln .wrapper $(basename $script)
done

Execution logs will be in /var/tmp/scriptLogs

Sorry for the delay in responding and thanks for all your responses.


So basically I am in the process of migrating from Solaris 5.9 to Linux.


We are in the build stage and the Linux system is currently run by another vendor who cannot/ will not confirm what scripts are currently running.


There are over 500 shell scripts on the old Solaris server and I have no idea which ones I need to migrate to Linux.


Hence the question about how do I know what is currently being executed.


I am in the process of wading through the crontabs but was looking for a more time effective method of identifying currently used scripts.


Cheers

Why not just copy over all the files (scripts) and be done with it for now?

That way you will not have many mistakes.

Alternatively, you might just move to a supported Solaris Version (11.4), or to an OpenSolaris now Illumos derivative...