Sponsored Content
Full Discussion: /usr/sbin/getty
Top Forums UNIX for Dummies Questions & Answers /usr/sbin/getty Post 32585 by iceman_denmark on Saturday 30th of November 2002 07:17:18 PM
Old 11-30-2002
Smilie It worked. Many thanx. Your are great. To reload the /etc/inittab I issued the command init q, which caused the system to re-examine the file and start a getty process. The proces was dead.
 

10 More Discussions You Might Find Interesting

1. Solaris

WARNING - /usr/sbin/fsck not found - Please help

WARNING - /usr/sbin/fsck not found. Most likely the mount of /usr failed or the /usr filesystem is badly damaged. The system is being halted. Either re-install the system of boot with -b option in an attempt to recover Anyone help me on restoring this without having to reinstall. it is a... (8 Replies)
Discussion started by: frustrated1
8 Replies

2. Solaris

different between /sbin/init and /usr/sbin/init

root@test09 # ls -al /sbin/init -r-xr-xr-x 1 root sys 550000 Jun 29 2002 /sbin/init root@test09 # ls -al /usr/sbin/init -r-xr-xr-x 1 root sys 37100 Jun 29 2002 /usr/sbin/init (2 Replies)
Discussion started by: userking
2 Replies

3. HP-UX

syslog: /usr/sbin/envd[1075]:

hi friends, what is the meaning of this error ? syslog: /usr/sbin/envd: (2 Replies)
Discussion started by: cromohawk
2 Replies

4. Solaris

crontab /usr/sbin/rtc log rc=1

I noticed in my cron log file for my solaris 8 servers the rc=1. I imagine that is return code and something did not process. Does anyone know what that is, is there fix or the implications of leaving it? Thank you > CMD: && /usr/sbin/rtc -c > /dev/null 2>&1 > root 22049 c Fri Dec 19... (1 Reply)
Discussion started by: csgonan
1 Replies

5. Red Hat

/usr/sbin/crond: can't lock /var/run/crond.pid,

please tell pre-requisite steps to activate cron. i activated the cron but it not executing the script which i set in crontab entry.through root user i passed the service crond start it get start.but when i go to etc/init.d and passed crond stop command.it gets crond: can't lock /var/run/crond.pid,... (2 Replies)
Discussion started by: umair
2 Replies

6. UNIX for Advanced & Expert Users

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0.0 is empty, not checked.

I thought I would document this error since its not documented very well. The package or file may be different but the idea is the same. $ sudo yum updateLoaded plugins: langpacks, presto, refresh-packagekit, versionlock Setting up Update Process Resolving Dependencies --> Running... (0 Replies)
Discussion started by: cokedude
0 Replies

7. Shell Programming and Scripting

Alternative for /usr/sbin/userdbset on Linux

Hello. I am currently on HPUX and migrating to Linux RHEL 6.4 This program on hpux: /usr/sbin/userdbset is puzzling me on linux. Does anyone know the equivilent program forked or used on linux. This program is mentioned in our user reset script. here is a strings of the... (2 Replies)
Discussion started by: olyanderson
2 Replies

8. AIX

/usr/sbin/extendvg: Unable to extend volume group

Dear Expret, Help me about my issue, I trying add new disk to volume Group but error: step add new disk to volume group. 1. ~Change a Volume Group Add a Physical Volume to a Volume Group Remove a Physical Volume from a Volume Group Reorganize a Volume Group... (6 Replies)
Discussion started by: williamen
6 Replies

9. HP-UX

HP-UX /usr/sbin/snmpdm logging level default?

Hi, I'm not an HP-UX SysAdmin and work with Linux Systems a bit more but I have a question about the logging level for the snmpdm. We don't specify or modify anything so we're probably taking the default? What is the default? I see in the man page these options are available: Turn off... (0 Replies)
Discussion started by: hlutz
0 Replies

10. Red Hat

"/usr/sbin/hpacucli ctrl all show" command does not work

Dear Concern, We have observed that following command stuck/does not work in some RedHat nodes. Please advise us to troubleshoot the issue. /usr/sbin/hpacucli ctrl all show Note: HP Array Configuration Utility CLI for Linux 64-bit With Best Regards, Md. Abdullah-Al Kauser (3 Replies)
Discussion started by: makauser
3 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 09:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy