Sponsored Content
Full Discussion: problem with login
Operating Systems AIX problem with login Post 302252418 by shockneck on Wednesday 29th of October 2008 11:12:50 AM
Old 10-29-2008
You might try this: boot the server in maintenance mode with a console attached to S1. Choose: Access a rootvg in maintenance mode, start a shell and mount a rootvg. In the shell export TERM=vt100 (or any other terminal suitable to your terminal program). Start smitty devices. Choose your TTY and change the following parameters:
* enable LOGIN - enable
* STTY attributes for RUN time - clocal (add)
* STTY attributes for LOGIN - clocal (add)
* Apply changes to Database only - yes
Then reboot.

hth
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

login problem

. HP-UX HPUX11I B.11.11 U 9000/778 (tb) telnetd: /usr/bin/login: No such file or directory Ok im currently logged into the machine and dont plan on logging out i found this out when i went to open another session on the box and was prompted with the above, i do not have a backup of the... (4 Replies)
Discussion started by: bbutler3295
4 Replies

2. Solaris

Login problem

Hi, I have a sun system. Currently reinstalled the OS. The TP interface is configured as hme0 by default when the OS got installed. I can ping locally. But when I try to login it gives me the belwo error message -- unable to login directly on the console. Please do let me know what could... (5 Replies)
Discussion started by: RajaRC
5 Replies

3. Red Hat

login problem

Dear friends, I am using linux redhat nash version 4.2.1.6 os. now i rebooted my system suddenly the following error is coming. INIT: canot execute /etc/X11/prefdm. INIT: canot execute /etc/X11/prefdm. INIT: canot execute /etc/X11/prefdm. after that it is asking login : ... (0 Replies)
Discussion started by: rajan_ka1
0 Replies

4. SCO

Problem when login

When I login on consola as root I have problem. I typed on login: root password:rootpassword then promt login: problem is for other users In sigle user mode I can login as root. Please halp me (1 Reply)
Discussion started by: draganmi
1 Replies

5. Linux

USER login problem

Hi All I am facing a login issue actually on my local machine users are not suppose to login with there respective prompt on the machine. Access deneid login as: daya Sent username "daya" daya@10.10.0.3's password: Access denied daya@192.168.0.83's password: and even i am not suppose... (3 Replies)
Discussion started by: daya.pandit
3 Replies

6. AIX

user login problem & Files listing problem.

1) when user login to the server the session got colosed. How will resolve? 2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem? Thanks in advance. (1 Reply)
Discussion started by: pernasivam
1 Replies

7. Linux

Login problem

Hi, If i changed my password then i can able to enter into linux box. After some time if i tried then i can able to enter into the same box. I have tried lot of times, But it is not resolved yet. Please advice for this . Error msg : fatal: Timeout before authentication for... (0 Replies)
Discussion started by: Mani_apr08
0 Replies

8. Ubuntu

login problem

Hi After I update my vga driver ubuntu stop to boot. When I restart my computer appear ubuntu first page and after he go to a black screen without any message. How I can restore of find problem? Thanks (6 Replies)
Discussion started by: nichol
6 Replies

9. Red Hat

Login problem

Hi Everybody, I am getting following error when am trying to login to my oracle user. su: warning: cannot change directory to /bin/bash: Not a directory -sh: /bin/bash/.profile: Not a directory -bash-3.1$ Please help me how to avoid this message and how to login with normal user login... (1 Reply)
Discussion started by: mastansaheb
1 Replies
INIT(8) 						      System Manager's Manual							   INIT(8)

NAME
init - process control initialization SYNOPSIS
/etc/init DESCRIPTION
Init is invoked inside UNIX as the last step in the boot procedure. It normally then runs the automatic reboot sequence as described in reboot(8), and if this succeeds, begins multi-user operation. If the reboot fails, it commences single user operation by giving the super- user a shell on the console. It is possible to pass parameters from the boot program to init so that single user operation is commenced immediately. When such single user operation is terminated by killing the single-user shell (i.e. by hitting ^D), init runs /etc/rc with- out the reboot parameter. This command file performs housekeeping operations such as removing temporary files, mounting file systems, and starting daemons. In multi-user operation, init's role is to create a process for each terminal port on which a user may log in. To begin such operations, it reads the file /etc/ttys and executes a command for each terminal specified in the file. This command will usually be /usr/libexec/getty. Getty opens and initializes the terminal line, reads the user's name and invokes login to log in the user and execute the Shell. Ultimately the Shell will terminate because of an end-of-file either typed explicitly or generated as a result of hanging up. The main path of init, which has been waiting for such an event, wakes up and removes the appropriate entry from the file utmp, which records cur- rent users, and makes an entry in the wtmp, file which maintains a history of logins and logouts. The wtmp entry is made only if a user logged in successfully on the line. Then the appropriate terminal is reopened and getty is reinvoked. Init catches the hangup signal (signal SIGHUP) and interprets it to mean that the file /etc/ttys should be read again. The Shell process on each line which used to be active in ttys but is no longer there is terminated; a new process is created for each added line; lines unchanged in the file are undisturbed. Thus it is possible to drop or add terminal lines without rebooting the system by changing the ttys file and sending a hangup signal to the init process: use `kill -HUP 1.' Init will terminate multi-user operations and resume single-user mode if sent a terminate (TERM) signal, i.e. ``kill -TERM 1''. If there are processes outstanding which are deadlocked (due to hardware or software failure), init will not wait for them all to die (which might take forever), but will time out after 30 seconds and print a warning message. Init will cease creating new getty's and allow the system to slowly die away, if it is sent a terminal stop (TSTP) signal, i.e. ``kill -TSTP 1''. A later hangup will resume full multi-user operations, or a terminate will initiate a single user shell. This hook is used by reboot(8) and halt(8). Init's role is so critical that if it dies, the system will reboot itself automatically. If, at bootstrap time, the init process cannot be located, the system will loop in user mode at location 0x13. DIAGNOSTICS
/usr/libexec/getty gettyargs failing, sleeping. A process being started to service a line is exiting quickly each time it is started. This is often caused by a ringing or noisy terminal line. Init will sleep for 30 seconds, then continue trying to start the process. WARNING: Something is hung (wont die); ps axl advised. A process is hung and could not be killed when the system was shutting down. This is usually caused by a process which is stuck in a device driver due to a persistent device error condition. FILES
/dev/console, /dev/tty*, /var/run/utmp, /usr/adm/wtmp, /etc/ttys, /etc/rc SEE ALSO
login(1), kill(1), sh(1), ttys(5), crash(8), getty(8), rc(8), reboot(8), halt(8), shutdown(8) 4th Berkeley Distribution November 27, 1996 INIT(8)
All times are GMT -4. The time now is 03:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy