Sponsored Content
Operating Systems HP-UX List running services, corresponding package name and status. Post 302930176 by RavinderSingh13 on Wednesday 31st of December 2014 04:33:55 AM
Old 12-31-2014
Hi Happy83,

Welcome to forums, kindly use code tags as per forum rules for commands/codes/inputs while posting. For your request:

HPUX does not have a similar utility.You would need to create your own init scripts. You can start with a copy of 1 of the init scripts and then make the necessary changes. Then make the additions to them. You can use /sbin/init.d/template file to create your own init scripts.


NOTE: you can go though the forum rules in following link too.
https://www.unix.com/misc.php?do=cfrules


Thanks,
R. Singh
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

List services running in UNIX

We have lost our Sys Admin and with the DST changes.. i need to make sure all services are re-started on a SUN server running SUNOS 5.9 How can i list what is running and make sure they are running after the DST patches are applied? (2 Replies)
Discussion started by: JanSP
2 Replies

2. Solaris

services status finding ...???

Could we find out the all services status in salaries 9 operating system....??? (2 Replies)
Discussion started by: udayn
2 Replies

3. UNIX for Dummies Questions & Answers

Running services, how to disable some?

Hello all happy people! :) Iam trying to figure out how to disable running services, and witch i can disable. Iam running ssh,apache,ftp and identd. Here is an output from nmap: 21/tcp open ftp Solaris ftpd 22/tcp open ssh SunSSH 1.1 (protocol 2.0) 23/tcp ... (2 Replies)
Discussion started by: empty
2 Replies

4. AIX

how to check status of various services and port?

How can i check which service is activated on my AIX Box? how one can check particular port is open or not (like ftp/telnet port)? I dont have admin rights (1 Reply)
Discussion started by: ashish4422
1 Replies

5. Shell Programming and Scripting

Colloring Status of process or package

Hi there all again, I am building a menu script for viewing packages and deamons and printers and all.. I know how to collor text to red or green. But I get my results from status and put it in a array. How can I change a result that is standing in a array to build collor around it. For... (6 Replies)
Discussion started by: draco
6 Replies

6. SuSE

Which command can be used to show running services?

Hi Dear Guys: I want to get a list of running services. Is there any command having this functionality? (3 Replies)
Discussion started by: crest.boy
3 Replies

7. UNIX for Advanced & Expert Users

detecting the running services

I did search on the subject on services in linux and they do explain how to find what are the services that loaded when the linux boot. however I have not find how to detect what services run right now. I would like to now that and how to kill services. Thanks. (3 Replies)
Discussion started by: programAngel
3 Replies

8. AIX

List running services, Package name and status on AIX.

Hi, How can I list running services, corresponding package name and status on the AIX host? On Linux (Centos), I use the below code snippet:- for i in `chkconfig --list | awk '{ print $1}'`; do status=`/sbin/service $i status` packagename=`rpm -qf /etc/init.d/$i` done Is there... (2 Replies)
Discussion started by: Vipin Batra
2 Replies

9. HP-UX

How to fetch all running services on HP-UX?

Hi All, I have a requirement to get all the running services on few HP-UX boxes. In Linux systems I am able to do that successfully using: chkconfig --list. However I can't find anything equivalent in HP-UX. If anyone has any pointers on the same then please suggest. Adyan (4 Replies)
Discussion started by: Adyan Faruqi
4 Replies

10. Solaris

Boot Error - NIS services fails with Status 96

My system suddenly crash and when it rebooted there was an error: /dev/rdsk/c1t0d0s3 is logging svc.startd: svc:/network/nis/client:default: Method "/method/yp" failed with status 96. The system completes booting however when I log in a user account / directory is not longer... (1 Reply)
Discussion started by: NeedSolarisHelp
1 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)
All times are GMT -4. The time now is 08:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy