I need to migrate the scripts to Linux but I would like to know which ones are currently being executed rather than migrating all 500 of them.
Is there a way in Solaris 5.9 to do this? I have googled and I believe there is a way in the later versions but not sure about this ancient version.
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:
Execution logs will be in /var/tmp/scriptLogs
These 2 Users Gave Thanks to jlliagre For This Post:
Hi There,
I have 3 scripts that have to be run one after the other. All 3 scripts are dependent of the other. Now, If I am about to run the second script, assuming that the first script has already been run, can I get the status of the first script.
The problem is that, My second script has... (11 Replies)
In the Java programme, I am calling function, "Runtime.getRuntime().exec( cmdarray ); " with the array of arguments in which first argument is the binary(C-executable) file and argv1,argv2 and so on. This will be executed on Sun OS system.. I can execute using "sh -c cmdarray" on the shell... (0 Replies)
Hello all,
I have a script callled 'ABCstartup' setup under /etc/rc.d/init.d
Softlink 'S91ABCstartup' pointing to above script has been created under /etc/rc.d/rc3.d
The script is not being executed when the server restarts.
The script runs successfully via manual execution:... (5 Replies)
Hi,
we have server, that is auditing actions executed, and then sends them to the syslog server.
But there is arguments to issued to the commands in the audit trail, but there is no such arguments in the syslog output on the syslog server!
Example - I executed:
# ls -la
audit... (1 Reply)
I have compiled my application on Solaris 10 with following description
SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320
The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
But when installing the application on Solaris 9
SunOS odcarch02 5.9... (2 Replies)
Hi,
I am looking for a script wherein i will be able to execute below procedures one by one in line and next procedures starts only when the previous one completes and also after execution of each procedure i will be getting a automted mail as "PL/SQL PROCEDURE SUCCESSFULLY EXCETUTED".
... (1 Reply)
Hi every one, i am new to shell script. my people given a task to write a shell script that should execute number of shell scripts in that. in that, if any shell script is failed to execute, we have to run the main script again, but the script should start execute from the failed script only..
it... (1 Reply)
Hi every one, i am new to shell script. my people given a task to write a shell script that should execute number of shell scripts in that. in that, if any shell script is failed to execute, we have to run the main script again, but the script should start execute from the failed script only..
it... (6 Replies)
Hi All, how to list all the commands executed by users on a linux server.... I dont have access to others .bash_history. and i am not root user.. Please help.. Thanks in advance.. (6 Replies)
Discussion started by: nanz143
6 Replies
LEARN ABOUT HPUX
init.d
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)