Sponsored Content
Full Discussion: Releasing a Port
Operating Systems AIX Releasing a Port Post 302425915 by bakunin on Monday 31st of May 2010 04:34:55 AM
Old 05-31-2010
Have a look at "/etc/inittab" to see which processes are started automatically during system startup. To configure the inittab do NOT use an editor, but the commands "rmitab" (delete), "lsitab" (list), "chitab" (change) and "mkitab" (create).

Issue a "lssrc -a" to get a list of all configured subsystems and compare this to what you found in "/etc/inittab".

Have a look at "/etc/inetd.conf" to see if there is any subserver configured.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. Programming

Problem with releasing semaphore lock

Hi, I am trying to write stuff to a shared memory using a writer, and reading the corresponding stuff using a reader. I am facing problems while releasing the lock, as a result of which I am having segmentation faults. The code is as follows... /********** writer.c ***********/ ... (1 Reply)
Discussion started by: jacques83
1 Replies

2. Solaris

Checking/ Releasing File Locks in Solaris

Hi, One of my prod jobs using Ab Initio (which is Solaris Based) returned this error: ========= Error from Reformat_3.000 on f7j21-01.xxxx3.com ========= Failed opening file for flow: Resource temporarily unavailable Flow = "Flow_11.000" connected to output port "out0" of "Reformat_3.000"... (0 Replies)
Discussion started by: teenu18
0 Replies

3. Linux

ext3 file system not releasing space

Hi all i am facing a problem with ext3 file system df -h is showing 19gb is used even if there is not a single file on the mount point /dev/mapper/vg01-archive 55G 19G 33G 36% /archive_log OS == Linux cdrsvr 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007... (1 Reply)
Discussion started by: ajays
1 Replies

4. Filesystems, Disks and Memory

Veritas HSM not releasing tapes

I have a volume managed by Veritas Storage Migrator 6.0 running on Solaris 10. It has one managed volume and one tape robot it shares with netpackup (separate volume pools). When I check the process tree I am not seeing any migration processes running, but when I check the panel on the tape robot... (0 Replies)
Discussion started by: ilikecows
0 Replies

5. Programming

Posix Semaphore Use - Releasing all resources?

I am attempting to write a program with multiple POSIX threads. I want to ensure all threads are released at the same time. I am (trying to) use a semaphore to accomplish this. Without too much irrelevant information, I declare my semaphore with 0 of 25 resources available. Is there a way... (7 Replies)
Discussion started by: snowbarr
7 Replies

6. Solaris

Releasing the swap space Solaris

Hi Guys ! I have found this problem many times that the swap space (/tmp space more precisely )of my Server becomes full specially when i run a complete back up of the server . once the /tmp space is full I am not able to run simple commands as i get error like : fork no space on... (6 Replies)
Discussion started by: Paarth
6 Replies

7. Solaris

Releasing the swap space Solaris

Hi Guys ! I have found this problem many times that the swap space (/tmp space more precisely )of my Server becomes full specially when i run a complete back up of the server . once the /tmp space is full I am not able to run simple commands as i get error like : fork no space on... (4 Replies)
Discussion started by: Paarth
4 Replies

8. AIX

AIX 6.1: Releasing Memory and Page Space

Hi everyone, i have a question about the Memory Management in AIX 6.1. I have - 128 GB RAM and - 70 GB Page Space. The application i am running on this machine is doing some operations in perl. These are done only once a day and uses both memory and paging space. My problem... (1 Reply)
Discussion started by: Haichao
1 Replies

9. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies

10. UNIX for Beginners Questions & Answers

PLINK from Windows not releasing job

Hi all, I would greatly appreciate some help with this. I may not even be on the right path but I think I am close. I have a Synology NAS that I am running rsync jobs on to offload to USB3. These work fine. I have backup software on our Windows Server 2008R2 that I have now realized can... (2 Replies)
Discussion started by: stefshuuj
2 Replies
inittab(4)						     Kernel Interfaces Manual							inittab(4)

NAME
inittab - Controls the initialization process SYNOPSIS
/etc/inittab DESCRIPTION
The inittab file provides the init program with instructions for creating and running initialization processes. The init program reads the inittab file each time init is invoked. The file typically contains instructions for the default initialization, the creation and control of processes at each run level, and the getty command, which controls the activation of terminal lines. Each line in the inittab file contains an entry that has four fields; each field is separated by a colon. There is no limit to the number of entries in the inittab file. The entry syntax is as follows: Identifier:Runlevel:Action:Command Specifies a fourteen character field used to uniquely identify an object. Specifies a twenty character field that defines the run levels in which the object is to be processed. Runlevel corresponds to a configuration of processes in a system. Each process spawned by the init command is assigned one or more run levels in which it is allowed to exist. The run levels are as follows: Specifies the halt state. Specifies multiuser state without network services. Specifies multiuser state with network services. Specifies single-user state. You can define multiple run levels for a process by specifying more than one run level character in any combination. Specifies a twenty char- acter field that tells init how to treat the specified process. init recognizes the following Action values: Specifies that if the process does not exist or if it dies, init starts it. If the process exists, init continues to process the inittab file. Specifies that if init enters a run level that matches the run level specified in the inittab file entry, it starts the process and waits for its termination. As long as init continues in this run level, it does not act on subsequent reads of the entry in the inittab file. Specifies that if init enters a run level that matches the run level specified in the inittab file, it starts the process and does not wait for its termination. When the process stops, init does not restart it. If init enters a new run level where the process is still running from a previous run- level change, init does not restart the process. Specifies that when init first executes and reads the inittab file, it processes this entry. The init program starts the process and does not wait for its termination. When the process stops, init does not restart it. The run level specified in this inittab file entry should be the default run level, or it must match the run level in which init operates at boot time. Specifies that when init first executes and reads the inittab file, it processes this inittab file entry. The init program starts the process, waits for its termination and, when it dies, does not restart the process. (This value exists only for SVID3/SVR4 com- patibility.) Specifies that if init receives the SIGPWR power fail signal, it executes the process associated with this line. (This value exists only for SVID3/SVR4 compatibility.) Specifies that if init receives the SIGPWR power fail signal, it executes the process associ- ated with this line and waits until the process terminates before continuing processing the inittab file. Specifies that if the process associated with this line is currently running, init sends the warning signal SIGTERM and waits 20 seconds before sending the kill signal SIGKILL. If the process does not existent, init ignores the inittab entry. Specifies that a line with this action is processed when init is originally invoked. The init program uses this line to determine the run level to enter originally. It determines this by taking the highest run level specified in the run level field and using that as its initial state. If the run level field is empty, this is inter- preted as 0s23, causing init to enter run level 3. If init does not find an initdefault entry in the inittab file, it requests an initial run level from the operator. Specifies that entries of this type are executed before init tries to access the console. This inittab file entry should be used only to initialize devices on which init could attempt to request a run level. Specifies a 1024 character field that contains the sh command to be executed. The command is prefixed with exec. Any legitimate sh syntax can appear in the command field. Com- ments can be inserted be specifying a number sign (#). The line continuation character can be placed at the end of a line. EXAMPLES
The following is an example of an inittab file entry for a terminal line: tty01:23:respawn:/usr/sbin/getty /dev/tty08 9600 vt100 FILES
Specifies the command that initializes and controls terminal lines. RELATED INFORMATION
Commands: init(8), getty(8) Functions: kill(2) delim off inittab(4)
All times are GMT -4. The time now is 05:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy