Sponsored Content
Top Forums Shell Programming and Scripting INIT Script Getting Executed Twice? Post 302905274 by Perderabo on Tuesday 10th of June 2014 03:56:44 PM
Old 06-10-2014
Post /etc/rc.status
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Init 6 & Init 0 problem

Hi Expert, I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0.. I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies

2. Shell Programming and Scripting

How to know who executed a script?

Dear all I would like to capture who executed a script to a script's variable (i.e. testing.sh), so I can save it to a log file. testing.sh #! bin/ksh user=`<< code here >>` // get the info below in RED color <<main logic>> echo "$user execute testing.sh on `date`" >> testing.log ... (2 Replies)
Discussion started by: on9west
2 Replies

3. Linux

How to I change init levels after typing init 1

Dear all, I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel): 1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies

4. UNIX for Advanced & Expert Users

Problem on init 0, execution is the same with init 6

Hi, I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS. When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies

5. Red Hat

init-script failing because of /etc/rc.d/init.d/functions

I encountered a problem on one of our database servers. OS: CentOS 5.5 final Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel) We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies

6. AIX

Script not getting executed via cron but executes when executed manually.

Hi Script not getting executed via cron but executes successfully when executed manually. Please assist cbspsap01(appuser) /app/scripts > cat restart.sh #!/bin/ksh cd /app/bin date >>logfile.out echo "Restart has been started....." >>logfile.out date >>logfile.out initfnsw -y restart... (3 Replies)
Discussion started by: samsungsamsung
3 Replies

7. Shell Programming and Scripting

Shell script executed from Informatica ETL tool is spawning 2 processes for one script

Hi, I am having a shell script which has a while loop as shown below. while do sleep 60 done I am executing this script from Informatica ETL tool command task from where we can execute UNIX commands/scripts. When i do that, i am seeing 2 processes getting started for one script... (2 Replies)
Discussion started by: chekusi
2 Replies

8. Shell Programming and Scripting

Start up init d script

Hi All, I'm trying to build a start up script, wud be gr8 if any one can explain what the below field means and how can i check it for my script. DAEMON_PATH="/home/wes/Development/projects/myapp" DAEMON=myapp DAEMONOPTS="-my opts" NAME=myapp DESC="My daemon description"... (4 Replies)
Discussion started by: Karthick N
4 Replies

9. Shell Programming and Scripting

Capture run time of python script executed inside shell script

I have bash shell script which is internally calling python script.I would like to know how long python is taking to execute.I am not allowed to do changes in python script.Please note i need to know execution time of python script which is getting executed inside shell .I need to store execution... (2 Replies)
Discussion started by: Adfire
2 Replies

10. Linux

Troubleshooting init.d script

This is what I did: 1. I wrote a simple init.d script (myscript.sh) 2. I placed it under /etc/init.d (where many other default scripts already are) 3. Set the perms to 755 4. Run: update-rc.d myscript.sh defaults I can run it perfectly by doing: /etc/init.d/myscript.sh start... (2 Replies)
Discussion started by: rlopes
2 Replies
stl_scp(4)						     Kernel Interfaces Manual							stl_scp(4)

NAME
stl_scp - Subset control program conventions for the setld utility DESCRIPTION
Each software subset that is distributed for the setld(8) command can have an associated subset control program. These programs perform the application-specific management operations that configure the subset into the system. Because subset control programs must be executed during installation to non-native file hierarchies, they must be written in an architecture-neutral language. Because these programs may also be required to run while the system is in the single-user run state, the interpreter must not use shared libraries. The use of /sbin/sh is strongly recommended. As subsets are installed and deleted, they pass through several system management states. Software is in the NEW state immediately after being extracted from the distribution media and verified. Software in this state is exactly as it was prepared for distribution by the software vendor. The subset control program is responsible for placing the software in the PROTOTYPE state at the request of setld. Software in this state is configured for use at a particular site. All of the software remains sharable but has undergone some level of customization. Software becomes runnable on a particular system and ceases to be sharable after it has been placed in the CONFIGURED state by the subset control program, again at the request of setld. Subset control programs are executed by setld to perform specific requested operations. Before executing a subset control program, setld sets the environment variable ACT to an action value. The subset control program is expected to inspect this variable and any command-line arguments to determine which actions to perform. The action values, the command-line arguments, and the behavior that setld expects are as follows: Configure subset The first command-line argument is a configuration message for the subset. The subset control program can interpret this message as it chooses. There are two reserved subset messages: Perform any management operations required to change the subset from the PROTO- TYPE state to the CONFIGURED state. Subset control programs called to perform this action must assume that the /usr file system is write locked and that the currently visible execution context (contents of /dev/kmem and so forth) is the same as that in which the application will execute. Perform any management operations required to change the subset from the CONFIGURED state to the PROTO- TYPE state. The execution environment is identical to that for C, INSTALL. Menu Request The first argument is one of -l or -x and specifies whether the user is installing or extracting software from the media. Determine if the subset is suitable for presentation to the user in the subset selection menu. If the subset is to be presented, the subset control program should return exit status 0. If the subset is not to be presented, the subset control program should return a nonzero status. Prepare for Deletion The subset is about to be deleted from the system. Perform any management operations required to change the subset from the PROTO- TYPE state to the NEW state. A nonzero return status can be returned to indicate that the subset should not be deleted. Prepare for Load The subset is about to be loaded onto the system. Verify that the system is ready for the subset to loaded from the installation media. A nonzero exit status can be returned to indicate that the subset should not be installed. Post Deletion Cleanup The subset control program should perform any management operations required to return the system to the state that it was in prior to installation of the subset. Post Load Configuration The subset has been loaded from the media and is on the system in the NEW state. The subset control program must change the subset from the NEW state to the PROTOTYPE state. Verify Subset The setld utility checks for the existence of the installed subset. If the subset exists, the setld utility verifies the size and checksum information for each file in the subset. If the subset control program includes any V phase processing, it is executed at this time. The setld utility does not execute subset control processing during the installation process. RELATED INFORMATION
setld(8) Guide to Preparing Product Kits delim off stl_scp(4)
All times are GMT -4. The time now is 03:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy